CVE-2026-43240
What it is
In the Linux kernel, the following vulnerability has been resolved: x86/kexec: add a sanity check on previous kernel's ima kexec buffer When the second-stage kernel is booted via kexec with a limiting command line such as "mem=<size>", the physical range that contains the carried over IMA measurement list may fall outside the truncated RAM leading to a kernel panic. BUG: unable to handle page fault for address: ffff97793ff47000 RIP: ima_restore_measurement_list+0xdc/0x45a #PF: error_code(0x0000) – not-present page Other architectures already validate the range with page_is_ram(), as done in commit cbf9c4b9617b ("of: check previous kernel's ima-kexec-buffer against memory bounds") do a similar check on x86. Without carrying the measurement list across kexec, the attestation would fail.
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
- Record status
- Modified
Affected
- 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
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-43240.md and follow it. Check whether this project is affected by CVE-2026-43240. 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/22e460b6333a5f818b042ac89201f8e735556f4a
- https://git.kernel.org/stable/c/37f18915a261afe84dab462624ed829cddb77a9b
- https://git.kernel.org/stable/c/4d7a8f5f28187e3d2958b2a134473da2665207e7
- https://git.kernel.org/stable/c/c5489d04337b47e93c0623e8145fcba3f5739efd
- https://git.kernel.org/stable/c/d4a132f121c591b60dbaf57ea91f1faf11631fbc
- https://git.kernel.org/stable/c/f8f73bf0f8a57ee9b86792456bd42079bc98c6b7
References
- https://git.kernel.org/stable/c/22e460b6333a5f818b042ac89201f8e735556f4a
- https://git.kernel.org/stable/c/37f18915a261afe84dab462624ed829cddb77a9b
- https://git.kernel.org/stable/c/4d7a8f5f28187e3d2958b2a134473da2665207e7
- https://git.kernel.org/stable/c/7e2476057950c174c7b2c2802246707bbfb497e4
- https://git.kernel.org/stable/c/c5489d04337b47e93c0623e8145fcba3f5739efd
- https://git.kernel.org/stable/c/d4a132f121c591b60dbaf57ea91f1faf11631fbc
- https://git.kernel.org/stable/c/f8f73bf0f8a57ee9b86792456bd42079bc98c6b7