VulnerabilityPublished 6 May 2026

CVE-2026-43171: Linux kernel · EFI/CPER: don't dump the entire memory region

Source GCVE Database

Not known to be exploited.

Data as of 27 Oct 2026, 02:02 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-v6h5-rjwv-4cvj

What to do

AI-suggested

A fix has been implemented in the Linux kernel to check the section length before dumping memory, preventing underflow and excessive memory dumps. Users should apply the official kernel update containing this fix once available. No alternative mitigations or workarounds are indicated.

Description

A vulnerability in the Linux kernel's EFI/CPER error handling code could cause excessive memory dumping, potential data disclosure, or kernel OOPS due to improper length checks when processing firmware error records.

Impact

The vulnerability can cause the kernel to spend excessive time dumping large memory regions, potentially disclose sensitive data from memory dumps, and may lead to kernel OOPS if the dump attempts to access unmapped memory regions.

Summary

CVE-2026-43171 addresses a flaw in the Linux kernel's cper_print_fw_err() function where the error record length is not properly validated against the offset. On systems with faulty firmware, this can cause an underflow in length calculation, leading to dumping of the entire memory region. This results in prolonged processing times, possible disclosure of sensitive memory contents, and kernel crashes if unmapped memory is accessed. The issue is fixed by adding checks to ensure the section length is sufficient before performing a hex dump.

References

Community reviews

Loading reviews…