CVE-2026-64372
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.10.261
- Linux Kernel < 5.15.212
- Linux Kernel < 6.1.178
- Linux Kernel < 6.6.145
- Linux Kernel < 6.12.96
- Linux Kernel < 6.18.39
- Linux Kernel < 7.1.4
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64372.md and follow it. Check whether this project is affected by CVE-2026-64372. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29
- https://git.kernel.org/stable/c/266d3dd8b757b48a576e90f018b51f7b7563cc32
- https://git.kernel.org/stable/c/5cdb25f144b101083d8bf3fd023ad87fbe6850d7
- https://git.kernel.org/stable/c/632666a63116d8061c62a988d1ca39dcd6d27c9b
- https://git.kernel.org/stable/c/6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7
- https://git.kernel.org/stable/c/8e454e9d0bc03446d610ee49abec9dfd424f6541
- https://git.kernel.org/stable/c/982c9f92d57bda2b769851ff6d90d43dcf5f3734
- https://git.kernel.org/stable/c/a36ca93a8ba57464e521d70a337d37f069064111
References
- https://git.kernel.org/stable/c/0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29
- https://git.kernel.org/stable/c/266d3dd8b757b48a576e90f018b51f7b7563cc32
- https://git.kernel.org/stable/c/5cdb25f144b101083d8bf3fd023ad87fbe6850d7
- https://git.kernel.org/stable/c/632666a63116d8061c62a988d1ca39dcd6d27c9b
- https://git.kernel.org/stable/c/6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7
- https://git.kernel.org/stable/c/8e454e9d0bc03446d610ee49abec9dfd424f6541
- https://git.kernel.org/stable/c/982c9f92d57bda2b769851ff6d90d43dcf5f3734
- https://git.kernel.org/stable/c/a36ca93a8ba57464e521d70a337d37f069064111