<?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:53:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72487 — PCI: Check ROM header and data structure addr before accessing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72487</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;PCI: Check ROM header and data structure addr before accessing&lt;/p&gt;
&lt;p&gt;We meet a crash when running stress-ng on x86_64 machine:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffa0000007f40000
  RIP: 0010:pci_get_rom_size+0x52/0x220
  Call Trace:
  &amp;lt;TASK&amp;gt;
    pci_map_rom+0x80/0x130
    pci_read_rom+0x4b/0xe0
    kernfs_file_read_iter+0x96/0x180
    vfs_read+0x1b1/0x300&lt;/p&gt;
&lt;p&gt;Our analysis reveals that the ROM space&amp;#39;s start address is
0xffa0000007f30000, and size is 0x10000. Because of broken ROM space,
before calling readl(pds), the pds&amp;#39;s value is 0xffa0000007f3ffff, which is
already pointed to the ROM space end, invoking readl() would read 4 bytes
therefore cause an out-of-bounds access and trigger a crash.  Fix this by
adding image header and data structure checking.&lt;/p&gt;
&lt;p&gt;We also found another crash on arm64 machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffff8000dd1393ff
  Mem abort info:
  ESR = 0x0000000096000021
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x21: alignment fault&lt;/p&gt;
&lt;p&gt;The call trace is the same with x86_64, but the crash reason is that the
data structure addr is not aligned with 4, and arm64 machine report
&amp;#34;alignment fault&amp;#34;. Fix this by adding alignment checking.&lt;/p&gt;
&lt;p&gt;[bhelgaas: shorten function names, wrap comments]&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;PCI: Check ROM header and data structure addr before accessing&lt;/p&gt;
&lt;p&gt;We meet a crash when running stress-ng on x86_64 machine:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffa0000007f40000
  RIP: 0010:pci_get_rom_size+0x52/0x220
  Call Trace:
  &amp;lt;TASK&amp;gt;
    pci_map_rom+0x80/0x130
    pci_read_rom+0x4b/0xe0
    kernfs_file_read_iter+0x96/0x180
    vfs_read+0x1b1/0x300&lt;/p&gt;
&lt;p&gt;Our analysis reveals that the ROM space&amp;#39;s start address is
0xffa0000007f30000, and size is 0x10000. Because of broken ROM space,
before calling readl(pds), the pds&amp;#39;s value is 0xffa0000007f3ffff, which is
already pointed to the ROM space end, invoking readl() would read 4 bytes
therefore cause an out-of-bounds access and trigger a crash.  Fix this by
adding image header and data structure checking.&lt;/p&gt;
&lt;p&gt;We also found another crash on arm64 machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address ffff8000dd1393ff
  Mem abort info:
  ESR = 0x0000000096000021
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x21: alignment fault&lt;/p&gt;
&lt;p&gt;The call trace is the same with x86_64, but the crash reason is that the
data structure addr is not aligned with 4, and arm64 machine report
&amp;#34;alignment fault&amp;#34;. Fix this by adding alignment checking.&lt;/p&gt;
&lt;p&gt;[bhelgaas: shorten function names, wrap comments]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72487</guid>
    </item>
  </channel>
</rss>
