VYPR
Medium severity5.5NVD Advisory· Published May 6, 2026· Updated May 11, 2026

CVE-2026-43240

CVE-2026-43240

Description

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=", 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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A missing physical memory bounds check in x86 kexec causes a kernel panic when the IMA measurement list buffer lies outside the truncated RAM after a kexec with 'mem=' restriction.

Root

Cause

In the Linux kernel's x86 architecture, the kexec mechanism lacked a sanity check to verify that the IMA measurement list buffer from the previous kernel resides within the usable physical memory of the new kernel. When a second-stage kernel is booted via kexec with a restrictive command line parameter like mem=, the truncated RAM may exclude the physical range containing the measurement list. This missing bounds validation leads to a kernel panic (page fault) when the new kernel attempts to restore the measurement list via ima_restore_measurement_list [1][2][3][4].

Exploitation

An attacker must have the ability to trigger a kexec operation with a limiting mem= kernel command line parameter. This typically requires root or equivalent privileges on the system. The attack does not require any network access; it is a local vulnerability. The specific condition is that the carried-over IMA buffer resides in a physical memory region that falls outside the new kernel's truncated address space.

Impact

The immediate impact is a kernel panic, resulting in a denial of service (DoS) on the targeted system. Additionally, because the IMA measurement list is not carried over successfully, attestation mechanisms that rely on the continuity of measurement records across kexec may fail, undermining security guarantees for measured boot.

Mitigation

The vulnerability has been patched in the Linux kernel stable tree through commits [1], [2], [3], and [4] which add a page_is_ram() check on the IMA buffer's physical range, similar to the existing validation on other architectures (as done in commit cbf9c4b9617b). Users should update to a kernel version containing these fixes or apply the patches manually.

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
    Range: >=6.0,<6.1.165

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

6

News mentions

0

No linked articles in our index yet.