CVE-2025-40034
Last modified
CVE-2025-40034 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: PCI/AER: Avoid NULL pointer dereference in aer_ratelimit() 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't advertise an AER Capability and therefore dev->aer_info, which contains AER stats and ratelimiting data, is NULL. pci_dev_aer_stats_incr() already checks dev->aer_info for NULL, but aer_ratelimit() did not, leading to NULL pointer dereferences like this one from the URL below: {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 [8086:2020] is an Intel "Sky Lake-E DMI3 Registers" device that claims to be a Root Port but does not advertise an AER Capability. Add a NULL check in aer_ratelimit() to avoid the NULL pointer dereference. Note that this also prevents ratelimiting these events from GHES. [bhelgaas: add crash details to commit log]. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: PCI/AER: Avoid NULL pointer dereference in aer_ratelimit() 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't advertise an AER Capability and therefore dev->aer_info, which contains AER stats and ratelimiting data, is NULL. pci_dev_aer_stats_incr() already checks dev->aer_info for NULL, but aer_ratelimit() did not, leading to NULL pointer dereferences like this one from the URL below: {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 [8086:2020] is an Intel "Sky Lake-E DMI3 Registers" device that claims to be a Root Port but does not advertise an AER Capability. Add a NULL check in aer_ratelimit() to avoid the NULL pointer dereference. Note that this also prevents ratelimiting these events from GHES. [bhelgaas: add crash details to commit log]
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a57f2bfb4a5863f83087867c0e671f2418212d23, < 41683624cbff0a26bb7e0627f4a7e1b51a8779a8; >= a57f2bfb4a5863f83087867c0e671f2418212d23, < deb2f228388ff3a9d0623e3b59a053e9235c341d |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-40034?
How severe is CVE-2025-40034?
How do I fix CVE-2025-40034?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-40029In the Linux kernel, the following vulnerability has been re…
- CVE-2025-4003A vulnerability was found in RefindPlusRepo RefindPlus 0.14.…6.8
- CVE-2025-40030In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40031In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40032In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40033In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40035In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40036In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40037In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40038In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-40039In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-4004A vulnerability was found in PHPGurukul COVID19 Testing Mana…9.8
Are you affected by CVE-2025-40034?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
