CVE-2026-64227

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. 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:

ACPI: driver: Check ACPI_COMPANION() against NULL during probe

Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), platform drivers that rely on the existence of a device's ACPI companion object should verify its presence.

Accordingly, add requisite ACPI_COMPANION() or ACPI_HANDLE() checks against NULL to 13 platform drivers handling core ACPI devices.

Also change the value returned by the ACPI thermal zone driver when the device's ACPI companion is not present to -ENODEV for consistency with the other drivers.

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
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 13, 2026

Advisory Details (4)

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

ACPI: driver: Check ACPI_COMPANION() against NULL during probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPI: driver: Check ACPI_COMPANION() against NULL during probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

ACPI: driver: Check ACPI_COMPANION() against NULL during probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/612ddab8fce04394bd7aebe8e0f2599642e30859
generic

ACPI: driver: Check ACPI_COMPANION() against NULL during probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34f4d0e4e5065237d15651df759a99e81b7f9f51

Vendor Advisories for CVE-2026-64227(2)

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

Patch Availability(3)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (139 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 22× in last 7d / 78× 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 101 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64227?
CVE-2026-64227 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ACPI: driver: Check ACPI_COMPANION() against NULL during probe Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of devicematchdriver_override(), platform drivers that…
When was CVE-2026-64227 disclosed?
CVE-2026-64227 was first published in the National Vulnerability Database on July 24, 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-64227 actively exploited?
CVE-2026-64227 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64227?
CVE-2026-64227 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64227, 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-64227

Explore →

Is Your Infrastructure Affected by CVE-2026-64227?

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