CyberSecBulletin
CVE-2026-64372NVD status: Modified

Linux: Use After Free

Published Updated By the CyberSecBulletin desk

CVE-2026-64372 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 8e454e9d0bc03446d610ee49abec9dfd424f6541, 632666a63116d8061c62a988d1ca39dcd6d27c9b, 5cdb25f144b101083d8bf3fd023ad87fbe6850d7 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 8e454e9d0bc03446d610ee49abec9dfd424f6541 or 632666a63116d8061c62a988d1ca39dcd6d27c9b or 5cdb25f144b101083d8bf3fd023ad87fbe6850d7 or 982c9f92d57bda2b769851ff6d90d43dcf5f3734, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.261 or 5.15.212 or 6.1.178 or 6.6.145, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 8e454e9d0bc03446d610ee49abec9dfd424f6541; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 632666a63116d8061c62a988d1ca39dcd6d27c9b; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 5cdb25f144b101083d8bf3fd023ad87fbe6850d7; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 982c9f92d57bda2b769851ff6d90d43dcf5f3734; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, a36ca93a8ba57464e521d70a337d37f069064111; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 0e3c739a2f6fc1de5b19a8839ab80696b9cb2a29; 0f1d683fb35d6c6f49ef696c95757f3970682a0e up to, but not including, 266d3dd8b757b48a576e90f018b51f7b7563cc32; and 1 more ranges8e454e9d0bc03446d610ee49abec9dfd424f6541, 632666a63116d8061c62a988d1ca39dcd6d27c9b, 5cdb25f144b101083d8bf3fd023ad87fbe6850d7, 982c9f92d57bda2b769851ff6d90d43dcf5f3734, a36ca93a8ba57464e521d70a337d37f069064111, 6ba6f6783be2ffeb2cbcdc9321c4b9f708f796f7
LinuxLinux Kernel2.6.34 up to, but not including, 5.10.261; 5.11 up to, but not including, 5.15.212; 5.16 up to, but not including, 6.1.178; 6.2 up to, but not including, 6.6.145; 6.7 up to, but not including, 6.12.96; 6.13 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.45.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use After Free vulnerabilities

Spotted an error? Tell us.