CVE-2026-64167: kho: skip KHO for crash kernel
In the Linux kernel, the following vulnerability has been resolved:
kho: skip KHO for crash kernel
khofillkimage() unconditionally populates the kimage with KHO metadata for every kexec image type. When the image is a crash kernel, this can be problematic as the crash kernel can run in a small reserved region and the KHO scratch areas can sit outside it. The crash kernel then faults during khomemoryinit() when it tries phystovirt() on the KHO FDT address:
Unable to handle kernel paging request at virtual address xxxxxxxx ... fdtoffsetptr+... fdtchecknodeoffset+... fdtfirstpropertyoffset+... fdtgetpropertynamelen+... fdtgetprop+... khomemoryinit+... mmcoreinit+... startkernel+...
kholocatememhole() already skips KHO logic for KEXECTYPECRASH images, but khofillkimage() was missing the same guard. As khofillkimage() is the single point that populates image->kho.fdt and image->kho.scratch, fixing it here is sufficient for both arm64 and x86 as the FDT and bootparams path are bailing out when these fields are unset.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64167?
CVE-2026-64167 has a risk rating of 23, indicating a moderate severity level.
What does CVE-2026-64167 affect?
CVE-2026-64167 affects the Linux kernel specifically related to crash kernel handling.
How do I fix CVE-2026-64167?
To fix CVE-2026-64167, update your Linux kernel to the latest patched version that resolves this vulnerability.
What are the risks associated with CVE-2026-64167?
The risks of CVE-2026-64167 include potential system instability when using crash kernels due to improper handling of KHO metadata.
When was CVE-2026-64167 published?
CVE-2026-64167 was published on July 19, 2026.