CVE-2026-64167

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

kho: skip KHO for crash kernel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6ac6721326a75ff2d14c68db05f93b576d8762f
generic

kho: skip KHO for crash kernel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6715d7ec472a476db17787697a4abda62962284

Vendor Advisories for CVE-2026-64167(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-08-30 02:44 UTCEG score recompute
  2. 2026-08-30 02:44 UTCVendor advisory
  3. 2026-08-30 02:44 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 11:47 UTCEG score recompute
  6. 2026-08-27 11:47 UTCVendor advisory
  7. 2026-08-27 11:46 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 05:46 UTCEG score recompute
  10. 2026-08-26 05:46 UTCVendor advisory
  11. 2026-08-26 05:46 UTCGHSA enrichment
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 04:44 UTCEG score recompute
  14. 2026-08-25 04:44 UTCVendor advisory
  15. 2026-08-25 04:44 UTCGHSA enrichment
  16. 2026-08-24 03:43 UTCVendor advisory
  17. 2026-08-24 03:43 UTCGHSA enrichment
  18. 2026-08-23 02:23 UTCEG score recompute
  19. 2026-08-23 02:23 UTCVendor advisory
  20. 2026-08-23 02:23 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 01:22 UTCEG score recompute
  23. 2026-08-22 01:22 UTCVendor advisory
  24. 2026-08-22 01:22 UTCGHSA enrichment
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 00:20 UTCEG score recompute
  2. 2026-08-21 00:20 UTCVendor advisory
  3. 2026-08-21 00:20 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 23:18 UTCEG score recompute
  6. 2026-08-19 23:18 UTCVendor advisory
  7. 2026-08-19 23:18 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 22:16 UTCEG score recompute
  10. 2026-08-18 22:16 UTCVendor advisory
  11. 2026-08-18 22:16 UTCGHSA enrichment
  12. 2026-08-17 21:05 UTCEG score recompute
  13. 2026-08-17 21:05 UTCVendor advisory
  14. 2026-08-17 21:05 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 19:12 UTCEG score recompute
  17. 2026-08-16 19:12 UTCVendor advisory
  18. 2026-08-16 19:12 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-15 17:39 UTCEG score recompute
  21. 2026-08-15 17:39 UTCVendor advisory
  22. 2026-08-15 17:39 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 16:37 UTCEG score recompute
  25. 2026-08-14 16:37 UTCVendor advisory
  26. 2026-08-14 16:37 UTCGHSA enrichment
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 15:36 UTCEG score recompute▲ 5.50
  29. 2026-08-13 15:36 UTCVendor advisory
  30. 2026-08-13 15:36 UTCGHSA enrichment
  31. 2026-08-13 15:36 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-11 14:59 UTCVendor advisory
  34. 2026-08-11 14:59 UTCGHSA enrichment
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-09 13:47 UTCEPSS rescore
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-08 15:04 UTCVendor advisory
  39. 2026-08-08 15:04 UTCGHSA enrichment
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-05 15:08 UTCVendor advisory
  44. 2026-08-05 15:08 UTCGHSA enrichment
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 10:39 UTCEPSS rescore
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 15:13 UTCVendor advisory
  49. 2026-08-02 15:13 UTCGHSA enrichment
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 15:18 UTCEG score recompute
  54. 2026-07-30 15:18 UTCGHSA enrichment
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-29 10:47 UTCGHSA enrichment
  58. 2026-07-28 15:37 UTCEPSS rescore
  59. 2026-07-27 14:14 UTCEPSS rescore
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 10:51 UTCEG score recompute
  63. 2026-07-26 10:51 UTCVendor advisory
  64. 2026-07-26 10:51 UTCGHSA enrichment
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-24 14:18 UTCEPSS rescore
  68. 2026-07-24 14:18 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 03:22 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-21 15:25 UTCEPSS rescore
  75. 2026-07-21 15:25 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64167?
CVE-2026-64167 is a medium vulnerability published on July 19, 2026. 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…
When was CVE-2026-64167 disclosed?
CVE-2026-64167 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64167 actively exploited?
CVE-2026-64167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64167?
CVE-2026-64167 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64167?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64167, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64167

Explore →

Is Your Infrastructure Affected by CVE-2026-64167?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs