Skip to main content

Linux Kernel CVE-2026-64167

| EUVDEUVD-2026-45852 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-19 Linux GHSA-8x2c-32p7-vm7c
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

AC:H reflects multi-condition dependency (KHO compiled in, kdump configured, crash event) not attacker-controlled; PR:L for local system presence; A:H for crash kernel fault.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
4.4 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Aug 13, 2026 - 16:13 vuln.today
CVSS changed
Aug 13, 2026 - 15:37 NVD
5.5 (MEDIUM)
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:40 nvd
MEDIUM 5.5

DescriptionNVD

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.

AnalysisAI

Crash kernel panic in Linux kernel's KHO (Kexec Handover) subsystem causes kdump capture to fail due to a missing crash-kernel guard in kho_fill_kimage(). Systems configured with both KHO and a crash kernel (kdump) are affected: when a kernel crash transfers control to the crash kernel, KHO metadata pointing outside the reserved crash region triggers an invalid phys_to_virt() translation in kho_memory_init(), crashing the crash kernel itself and defeating the crash dump mechanism. No public exploit exists and EPSS at 0.16% (6th percentile) reflects appropriately low exploitation probability given the local-only, configuration-dependent nature of the flaw.

Technical ContextAI

The Linux kernel's KHO (Kexec Handover) subsystem preserves kernel state across kexec reboots by populating kimage structures with FDT (Flattened Device Tree) metadata and scratch memory areas. The vulnerable function kho_fill_kimage() did not distinguish between standard kexec images and crash (kdump) images of type KEXEC_TYPE_CRASH, unconditionally writing image->kho.fdt and image->kho.scratch for all image types. Crash kernels boot within a tightly bounded physical memory reservation declared via the crashkernel= parameter; KHO scratch allocations may reside outside this region. When the crash kernel's kho_memory_init() calls phys_to_virt() on the KHO FDT address, the physical address is not mapped into the crash kernel's reduced virtual address space, producing an unhandled kernel paging fault. Crucially, kho_locate_mem_hole() already contained the KEXEC_TYPE_CRASH guard, but kho_fill_kimage() - the sole point that sets these fields - was missing the equivalent check. CWE-476 is applied, though the fault is technically an invalid virtual address from a bad physical-to-virtual translation rather than a strict null pointer dereference. Affected CPE: cpe:2.3:a:linux:linux:* across multiple stable branches including 6.19 and pre-patch 7.x series.

RemediationAI

The primary fix is to upgrade to Linux kernel 7.1 or 7.0.11 (stable branch), which include the correcting commits a6715d7ec472a476db17787697a4abda62962284 and a6ac6721326a75ff2d14c68db05f93b576d8762f available at https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f and https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284. Ubuntu users should apply the update from USN-8593-1 at https://ubuntu.com/security/notices/USN-8593-1. As a compensating control, removing the crashkernel= kernel parameter disables kdump entirely and eliminates the trigger condition, at the cost of losing crash dump capability - a significant trade-off on systems where post-mortem kernel debugging is required. Alternatively, if KHO is not needed operationally, rebuilding the kernel without KHO support (CONFIG_KEXEC_HANDOVER=n) prevents the faulty code path from being compiled in. Both workarounds carry functional costs and patching is preferred.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-64167 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy