CVE-2026-64372

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation

pcc_cpufreq_do_osc() calls acpi_evaluate_object() twice for the two-phase _OSC negotiation. Between the two calls it freed output.pointer but left output.length unchanged. Since acpi_evaluate_object() treats a non-zero length with a non-NULL pointer as an existing buffer to write into, the second call wrote into freed memory (use-after-free). The subsequent kfree(output.pointer) at out_free then freed the same pointer a second time (double free).

Reset output.pointer to NULL and output.length to ACPI_ALLOCATE_BUFFER after freeing the first result, so ACPICA allocates a fresh buffer for each phase independently.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

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

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/982c9f92d57bda2b769851ff6d90d43dcf5f3734
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e454e9d0bc03446d610ee49abec9dfd424f6541
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/632666a63116d8061c62a988d1ca39dcd6d27c9b
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5cdb25f144b101083d8bf3fd023ad87fbe6850d7
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/266d3dd8b757b48a576e90f018b51f7b7563cc32
generic

cpufreq: pcc: fix use-after-free and double free in _OSC evaluation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29

Vendor Advisories for CVE-2026-64372(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 28× in last 7d / 145× 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 175 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64372?
CVE-2026-64372 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation pcccpufreqdoosc() calls acpievaluate_object() twice for the two-phase _OSC negotiation. Between the two calls it freed output.pointer but left output.length…
When was CVE-2026-64372 disclosed?
CVE-2026-64372 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64372 actively exploited?
CVE-2026-64372 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64372?
CVE-2026-64372 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64372, 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-64372

Explore →

Is Your Infrastructure Affected by CVE-2026-64372?

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

Start Free Scan →Browse All CVEs