x86/kexec: add a sanity check on previous kernel's ima kexec buffer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
6.0
References 7
git.kernel.org
- stable/c/37f18915a261afe84dab462624ed829cddb77a9b
- stable/c/22e460b6333a5f818b042ac89201f8e735556f4a
- stable/c/7e2476057950c174c7b2c2802246707bbfb497e4
- stable/c/f8f73bf0f8a57ee9b86792456bd42079bc98c6b7
- stable/c/d4a132f121c591b60dbaf57ea91f1faf11631fbc
- stable/c/4d7a8f5f28187e3d2958b2a134473da2665207e7
- stable/c/c5489d04337b47e93c0623e8145fcba3f5739efd