CVE-2026-64167 (GCVE-0-2026-64167)

Vulnerability from cvelistv5 – Published: 2026-07-19 15:40 – Updated: 2026-07-19 15:40
VLAI
Title
kho: skip KHO for crash kernel
Summary
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.
Severity
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: d7255959b69a4e727c61eb04231d11390d4f391e , < a6ac6721326a75ff2d14c68db05f93b576d8762f (git)
Affected: d7255959b69a4e727c61eb04231d11390d4f391e , < a6715d7ec472a476db17787697a4abda62962284 (git)
Create a notification for this product.
Linux Linux Affected: 6.19
Unaffected: 0 , < 6.19 (semver)
Unaffected: 7.0.11 , ≤ 7.0.* (semver)
Unaffected: 7.1 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "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-\u003ekho.fdt\nand image-\u003ekho.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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-64167",
      "date": "2026-07-20",
      "epss": "0.00161",
      "percentile": "0.05697"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-64167\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-07-19T16:17:58.833\",\"lastModified\":\"2026-07-19T16:17:58.833\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"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-\u003ekho.fdt\\nand image-\u003ekho.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.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"kernel/liveupdate/kexec_handover.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"d7255959b69a4e727c61eb04231d11390d4f391e\",\"lessThan\":\"a6ac6721326a75ff2d14c68db05f93b576d8762f\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"d7255959b69a4e727c61eb04231d11390d4f391e\",\"lessThan\":\"a6715d7ec472a476db17787697a4abda62962284\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"kernel/liveupdate/kexec_handover.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.19\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.19\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0.11\",\"lessThanOrEqual\":\"7.0.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.