CVE-2026-43171
What it is
In the Linux kernel, the following vulnerability has been resolved: EFI/CPER: don't dump the entire memory region The current logic at cper_print_fw_err() doesn't check if the error record length is big enough to handle offset. On a bad firmware, if the ofset is above the actual record, length -= offset will underflow, making it dump the entire memory. The end result can be: - the logic taking a lot of time dumping large regions of memory; - data disclosure due to the memory dumps; - an OOPS, if it tries to dump an unmapped memory region. Fix it by checking if the section length is too small before doing a hex dump. [ rjw: Subject tweaks ]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-191
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.252
- Linux Kernel < 5.15.202
- Linux Kernel < 6.1.165
- Linux Kernel < 6.6.128
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
- Linux Kernel 5.7
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43171.md and follow it. Check whether this project is affected by CVE-2026-43171. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/02de64ab54b4bb0f1b21bb324aeff3b08612be33
- https://git.kernel.org/stable/c/0e09b522f2622841389c3b2f9ac4969e35c0809d
- https://git.kernel.org/stable/c/54e131db4cdffd946db890ff33ff2647053fd4f6
- https://git.kernel.org/stable/c/55cc6fe5716f678f06bcb95140882dfa684464ec
- https://git.kernel.org/stable/c/5a9b1dda8481b82851a655c3bcc5b44879b95334
- https://git.kernel.org/stable/c/64ae5aaa7ac93c83da456039e8ec747bfa8a7cff
- https://git.kernel.org/stable/c/7780c0bad2a3a70a8c0113a33c02f4151d901eb3
- https://git.kernel.org/stable/c/a8419f5f2c5f2d80848ddabb2b95cf0da84a5f91
References
- https://git.kernel.org/stable/c/02de64ab54b4bb0f1b21bb324aeff3b08612be33
- https://git.kernel.org/stable/c/0e09b522f2622841389c3b2f9ac4969e35c0809d
- https://git.kernel.org/stable/c/54e131db4cdffd946db890ff33ff2647053fd4f6
- https://git.kernel.org/stable/c/55cc6fe5716f678f06bcb95140882dfa684464ec
- https://git.kernel.org/stable/c/5a9b1dda8481b82851a655c3bcc5b44879b95334
- https://git.kernel.org/stable/c/64ae5aaa7ac93c83da456039e8ec747bfa8a7cff
- https://git.kernel.org/stable/c/7780c0bad2a3a70a8c0113a33c02f4151d901eb3
- https://git.kernel.org/stable/c/a8419f5f2c5f2d80848ddabb2b95cf0da84a5f91