Kernel memory corruption via stale ACPI buffer
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in the Linux Kernel PCC cpufreq driver allows local users to corrupt kernel memory during ACPI _OSC negotiation. pcc_cpufreq_do_osc() frees the first result buffer but retains its pointer and nonzero length, so the second acpi_evaluate_object() call writes into freed memory before the cleanup path frees it again. Reachability requires an x86 system exposing the PCC ACPI objects; successful corruption permits kernel data modification or disclosure and can crash the kernel.
Summary
What happened
Use-after-free in the Linux Kernel PCC cpufreq driver allows local users to corrupt kernel memory during ACPI _OSC negotiation. pcc_cpufreq_do_osc() frees the first result buffer but retains its pointer and nonzero length, so the second acpi_evaluate_object() call writes into freed memory before the cleanup path frees it again. Reachability requires an x86 system exposing the PCC ACPI objects; successful corruption permits kernel data modification or disclosure and can crash the kernel.
The record
- CVE
- CVE-2026-64372
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <266d3dd8b757b48a576e90f018b51f7b7563cc32
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <5cdb25f144b101083d8bf3fd023ad87fbe6850d7
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <632666a63116d8061c62a988d1ca39dcd6d27c9b
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <8e454e9d0bc03446d610ee49abec9dfd424f6541
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <982c9f92d57bda2b769851ff6d90d43dcf5f3734
- Affected versionversion=0f1d683fb35d6c6f49ef696c95757f3970682a0e <a36ca93a8ba57464e521d70a337d37f069064111
- Affected versionversion=2.6.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo