<?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>Mon, 28 Sep 2026 18:39:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40034 — PCI/AER: Avoid NULL pointer dereference in aer_ratelimit()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40034</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/AER: Avoid NULL pointer dereference in aer_ratelimit()&lt;/p&gt;
&lt;p&gt;When platform firmware supplies error information to the OS, e.g., via the
ACPI APEI GHES mechanism, it may identify an error source device that
doesn&amp;#39;t advertise an AER Capability and therefore dev-&amp;gt;aer_info, which
contains AER stats and ratelimiting data, is NULL.&lt;/p&gt;
&lt;p&gt;pci_dev_aer_stats_incr() already checks dev-&amp;gt;aer_info for NULL, but
aer_ratelimit() did not, leading to NULL pointer dereferences like this one
from the URL below:&lt;/p&gt;
&lt;p&gt;{1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
  {1}[Hardware Error]: event severity: corrected
  {1}[Hardware Error]:   device_id: 0000:00:00.0
  {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2020
  {1}[Hardware Error]:   aer_cor_status: 0x00001000, aer_cor_mask: 0x00002000
  BUG: kernel NULL pointer dereference, address: 0000000000000264
  RIP: 0010:___ratelimit+0xc/0x1b0
  pci_print_aer+0x141/0x360
  aer_recover_work_func+0xb5/0x130&lt;/p&gt;
&lt;p&gt;[8086:2020] is an Intel &amp;#34;Sky Lake-E DMI3 Registers&amp;#34; device that claims to
be a Root Port but does not advertise an AER Capability.&lt;/p&gt;
&lt;p&gt;Add a NULL check in aer_ratelimit() to avoid the NULL pointer dereference.
Note that this also prevents ratelimiting these events from GHES.&lt;/p&gt;
&lt;p&gt;[bhelgaas: add crash details to commit log]&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/AER: Avoid NULL pointer dereference in aer_ratelimit()&lt;/p&gt;
&lt;p&gt;When platform firmware supplies error information to the OS, e.g., via the
ACPI APEI GHES mechanism, it may identify an error source device that
doesn&amp;#39;t advertise an AER Capability and therefore dev-&amp;gt;aer_info, which
contains AER stats and ratelimiting data, is NULL.&lt;/p&gt;
&lt;p&gt;pci_dev_aer_stats_incr() already checks dev-&amp;gt;aer_info for NULL, but
aer_ratelimit() did not, leading to NULL pointer dereferences like this one
from the URL below:&lt;/p&gt;
&lt;p&gt;{1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
  {1}[Hardware Error]: event severity: corrected
  {1}[Hardware Error]:   device_id: 0000:00:00.0
  {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2020
  {1}[Hardware Error]:   aer_cor_status: 0x00001000, aer_cor_mask: 0x00002000
  BUG: kernel NULL pointer dereference, address: 0000000000000264
  RIP: 0010:___ratelimit+0xc/0x1b0
  pci_print_aer+0x141/0x360
  aer_recover_work_func+0xb5/0x130&lt;/p&gt;
&lt;p&gt;[8086:2020] is an Intel &amp;#34;Sky Lake-E DMI3 Registers&amp;#34; device that claims to
be a Root Port but does not advertise an AER Capability.&lt;/p&gt;
&lt;p&gt;Add a NULL check in aer_ratelimit() to avoid the NULL pointer dereference.
Note that this also prevents ratelimiting these events from GHES.&lt;/p&gt;
&lt;p&gt;[bhelgaas: add crash details to commit log]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40034</guid>
    </item>
  </channel>
</rss>
