CVE-2026-64167
Last modified
CVE-2026-64167 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: kho: skip KHO for crash kernel kho_fill_kimage() 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 kho_memory_init() when it tries phys_to_virt() on the KHO FDT address: Unable to handle kernel paging request at virtual address xxxxxxxx ... fdt_offset_ptr+... fdt_check_node_offset_+... fdt_first_property_offset+... fdt_get_property_namelen_+... fdt_getprop+... kho_memory_init+... mm_core_init+... start_kernel+... kho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH images, but kho_fill_kimage() was missing the same guard. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: kho: skip KHO for crash kernel kho_fill_kimage() 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 kho_memory_init() when it tries phys_to_virt() on the KHO FDT address: Unable to handle kernel paging request at virtual address xxxxxxxx ... fdt_offset_ptr+... fdt_check_node_offset_+... fdt_first_property_offset+... fdt_get_property_namelen_+... fdt_getprop+... kho_memory_init+... mm_core_init+... start_kernel+... kho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH images, but kho_fill_kimage() was missing the same guard. As kho_fill_kimage() 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 boot_params path are bailing out when these fields are unset.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= d7255959b69a4e727c61eb04231d11390d4f391e, < a6ac6721326a75ff2d14c68db05f93b576d8762f; >= d7255959b69a4e727c61eb04231d11390d4f391e, < a6715d7ec472a476db17787697a4abda62962284 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64167?
How severe is CVE-2026-64167?
How do I fix CVE-2026-64167?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64161In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64162In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64163In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64164In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64165In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64166In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64168In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64169In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6417The GLS Shipping for WooCommerce plugin for WordPress is vul…6.1
- CVE-2026-64170In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64171In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64172In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-64167?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
