{"api_version":"1","generated_at":"2026-07-20T14:42:03+00:00","cve":"CVE-2026-64167","urls":{"html":"https://cve.report/CVE-2026-64167","api":"https://cve.report/api/cve/CVE-2026-64167.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64167","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64167"},"summary":{"title":"kho: skip KHO for crash kernel","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkho: skip KHO for crash kernel\n\nkho_fill_kimage() unconditionally populates the kimage with KHO\nmetadata for every kexec image type. When the image is a crash kernel,\nthis can be problematic as the crash kernel can run in a small reserved\nregion and the KHO scratch areas can sit outside it.\nThe crash kernel then faults during kho_memory_init() when it\ntries phys_to_virt() on the KHO FDT address:\n\n  Unable to handle kernel paging request at virtual address xxxxxxxx\n  ...\n    fdt_offset_ptr+...\n    fdt_check_node_offset_+...\n    fdt_first_property_offset+...\n    fdt_get_property_namelen_+...\n    fdt_getprop+...\n    kho_memory_init+...\n    mm_core_init+...\n    start_kernel+...\n\nkho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH\nimages, but kho_fill_kimage() was missing the same guard. As\nkho_fill_kimage() is the single point that populates image->kho.fdt\nand image->kho.scratch, fixing it here is sufficient for both arm64\nand x86 as the FDT and boot_params path are bailing out when these\nfields are unset.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-19 16:17:58","updated_at":"2026-07-19 16:17:58"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284","name":"https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f","name":"https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64167","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64167","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d7255959b69a4e727c61eb04231d11390d4f391e a6ac6721326a75ff2d14c68db05f93b576d8762f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d7255959b69a4e727c61eb04231d11390d4f391e a6715d7ec472a476db17787697a4abda62962284 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.11 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/liveupdate/kexec_handover.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a6ac6721326a75ff2d14c68db05f93b576d8762f","status":"affected","version":"d7255959b69a4e727c61eb04231d11390d4f391e","versionType":"git"},{"lessThan":"a6715d7ec472a476db17787697a4abda62962284","status":"affected","version":"d7255959b69a4e727c61eb04231d11390d4f391e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/liveupdate/kexec_handover.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.11","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nkho: skip KHO for crash kernel\n\nkho_fill_kimage() unconditionally populates the kimage with KHO\nmetadata for every kexec image type. When the image is a crash kernel,\nthis can be problematic as the crash kernel can run in a small reserved\nregion and the KHO scratch areas can sit outside it.\nThe crash kernel then faults during kho_memory_init() when it\ntries phys_to_virt() on the KHO FDT address:\n\n  Unable to handle kernel paging request at virtual address xxxxxxxx\n  ...\n    fdt_offset_ptr+...\n    fdt_check_node_offset_+...\n    fdt_first_property_offset+...\n    fdt_get_property_namelen_+...\n    fdt_getprop+...\n    kho_memory_init+...\n    mm_core_init+...\n    start_kernel+...\n\nkho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH\nimages, but kho_fill_kimage() was missing the same guard. As\nkho_fill_kimage() is the single point that populates image->kho.fdt\nand image->kho.scratch, fixing it here is sufficient for both arm64\nand x86 as the FDT and boot_params path are bailing out when these\nfields are unset."}],"providerMetadata":{"dateUpdated":"2026-07-19T15:40:52.023Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f"},{"url":"https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284"}],"title":"kho: skip KHO for crash kernel","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64167","datePublished":"2026-07-19T15:40:52.023Z","dateReserved":"2026-07-19T07:54:57.038Z","dateUpdated":"2026-07-19T15:40:52.023Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-19 16:17:58","lastModifiedDate":"2026-07-19 16:17:58","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64167","Ordinal":"1","Title":"kho: skip KHO for crash kernel","CVE":"CVE-2026-64167","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64167","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nkho: skip KHO for crash kernel\n\nkho_fill_kimage() unconditionally populates the kimage with KHO\nmetadata for every kexec image type. When the image is a crash kernel,\nthis can be problematic as the crash kernel can run in a small reserved\nregion and the KHO scratch areas can sit outside it.\nThe crash kernel then faults during kho_memory_init() when it\ntries phys_to_virt() on the KHO FDT address:\n\n  Unable to handle kernel paging request at virtual address xxxxxxxx\n  ...\n    fdt_offset_ptr+...\n    fdt_check_node_offset_+...\n    fdt_first_property_offset+...\n    fdt_get_property_namelen_+...\n    fdt_getprop+...\n    kho_memory_init+...\n    mm_core_init+...\n    start_kernel+...\n\nkho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH\nimages, but kho_fill_kimage() was missing the same guard. As\nkho_fill_kimage() is the single point that populates image->kho.fdt\nand image->kho.scratch, fixing it here is sufficient for both arm64\nand x86 as the FDT and boot_params path are bailing out when these\nfields are unset.","Type":"Description","Title":"kho: skip KHO for crash kernel"}]}}}