Linux: Double Free
CVE-2026-64377 is a high-severity double 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 0f012938f21302c08153589c1aca0283f8d6911d, 28a03a3f6e6cda0b0da3b43761d175dec5d14d13, e904961332801c87355f5d11c65bb433e717c489 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 0f012938f21302c08153589c1aca0283f8d6911d or 28a03a3f6e6cda0b0da3b43761d175dec5d14d13 or e904961332801c87355f5d11c65bb433e717c489 or 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.96 or 6.18.39 or 7.1.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 054a3ef683a176a509cc9b37f762029aae942495 up to, but not including, 0f012938f21302c08153589c1aca0283f8d6911d; 054a3ef683a176a509cc9b37f762029aae942495 up to, but not including, 28a03a3f6e6cda0b0da3b43761d175dec5d14d13; 054a3ef683a176a509cc9b37f762029aae942495 up to, but not including, e904961332801c87355f5d11c65bb433e717c489; 054a3ef683a176a509cc9b37f762029aae942495 up to, but not including, 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; 054a3ef683a176a509cc9b37f762029aae942495 up to, but not including, bcb8889c4981fdde42d4fd2c29a77d510fe21da2; 6.2 | 0f012938f21302c08153589c1aca0283f8d6911d, 28a03a3f6e6cda0b0da3b43761d175dec5d14d13, e904961332801c87355f5d11c65bb433e717c489, 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d, bcb8889c4981fdde42d4fd2c29a77d510fe21da2 |
| Linux | Linux Kernel | 6.2 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.4 | 6.12.96, 6.18.39, 7.1.4 |
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 NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Double Free
The product calls free() twice on the same memory address.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
- Use a static analysis tool to find double free instances.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Double Free vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.