<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 04:55:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38427 — video: screen_info: Relocate framebuffers behind PCI bridges</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38427</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: screen_info: Relocate framebuffers behind PCI bridges&lt;/p&gt;
&lt;p&gt;Apply PCI host-bridge window offsets to screen_info framebuffers. Fixes
invalid access to I/O memory.&lt;/p&gt;
&lt;p&gt;Resources behind a PCI host bridge can be relocated by a certain offset
in the kernel&amp;#39;s CPU address range used for I/O. The framebuffer memory
range stored in screen_info refers to the CPU addresses as seen during
boot (where the offset is 0). During boot up, firmware may assign a
different memory offset to the PCI host bridge and thereby relocating
the framebuffer address of the PCI graphics device as seen by the kernel.
The information in screen_info must be updated as well.&lt;/p&gt;
&lt;p&gt;The helper pcibios_bus_to_resource() performs the relocation of the
screen_info&amp;#39;s framebuffer resource (given in PCI bus addresses). The
result matches the I/O-memory resource of the PCI graphics device (given
in CPU addresses). As before, we store away the information necessary to
later update the information in screen_info itself.&lt;/p&gt;
&lt;p&gt;Commit 78aa89d1dfba (&amp;#34;firmware/sysfb: Update screen_info for relocated
EFI framebuffers&amp;#34;) added the code for updating screen_info. It is based
on similar functionality that pre-existed in efifb. Efifb uses a pointer
to the PCI resource, while the newer code does a memcpy of the region.
Hence efifb sees any updates to the PCI resource and avoids the issue.&lt;/p&gt;
&lt;p&gt;v3:
- Only use struct pci_bus_region for PCI bus addresses (Bjorn)
- Clarify address se…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: screen_info: Relocate framebuffers behind PCI bridges&lt;/p&gt;
&lt;p&gt;Apply PCI host-bridge window offsets to screen_info framebuffers. Fixes
invalid access to I/O memory.&lt;/p&gt;
&lt;p&gt;Resources behind a PCI host bridge can be relocated by a certain offset
in the kernel&amp;#39;s CPU address range used for I/O. The framebuffer memory
range stored in screen_info refers to the CPU addresses as seen during
boot (where the offset is 0). During boot up, firmware may assign a
different memory offset to the PCI host bridge and thereby relocating
the framebuffer address of the PCI graphics device as seen by the kernel.
The information in screen_info must be updated as well.&lt;/p&gt;
&lt;p&gt;The helper pcibios_bus_to_resource() performs the relocation of the
screen_info&amp;#39;s framebuffer resource (given in PCI bus addresses). The
result matches the I/O-memory resource of the PCI graphics device (given
in CPU addresses). As before, we store away the information necessary to
later update the information in screen_info itself.&lt;/p&gt;
&lt;p&gt;Commit 78aa89d1dfba (&amp;#34;firmware/sysfb: Update screen_info for relocated
EFI framebuffers&amp;#34;) added the code for updating screen_info. It is based
on similar functionality that pre-existed in efifb. Efifb uses a pointer
to the PCI resource, while the newer code does a memcpy of the region.
Hence efifb sees any updates to the PCI resource and avoids the issue.&lt;/p&gt;
&lt;p&gt;v3:
- Only use struct pci_bus_region for PCI bus addresses (Bjorn)
- Clarify address se…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38427</guid>
    </item>
  </channel>
</rss>
