Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40034: PCI/AER: Avoid NULL pointer dereference in aer_ratelimit()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 41683624cbff0a26bb7e0627f4a7e1b51a8779a8, deb2f228388ff3a9d0623e3b59a053e9235c341d.

Low priority for now. Upgrade to Linux Linux 41683624cbff0a26bb7e0627f4a7e1b51a8779a8, deb2f228388ff3a9d0623e3b59a053e9235c341d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

—No exploit Fix available
Published
Oct 28, 2025
Updated
Oct 19, 2026
EPSS
0.2% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40034

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.16affected
    • a57f2bfb4a5863f83087867c0e671f2418212d23 and later · before 41683624cbff0a26bb7e0627f4a7e1b51a8779a8affected · git
    • a57f2bfb4a5863f83087867c0e671f2418212d23 and later · before deb2f228388ff3a9d0623e3b59a053e9235c341daffected · git
    • before 6.16not affected · semver
    • 6.17.3 and later · up to and including 6.17.*not affected · semver
    • 6.18 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40032Oct 28, 2025 · PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release
    0Monitor
  • ← EarlierCVE-2025-40033Oct 28, 2025 · remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable()
    0Monitor
  • Later →CVE-2025-40035Oct 28, 2025 · Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux41683624cbff0a26bb7e0627f4a7e1b51a8779a8Vendor (CNA)
Linux Linuxdeb2f228388ff3a9d0623e3b59a053e9235c341dVendor (CNA)
almalinux:kernel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.17.6-1 · Debian:14Package registry (OSV)
opensuse:kernel-source6.17.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records