CVE-2026-64377
Last modified
CVE-2026-64377 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 054a3ef683a176a509cc9b37f762029aae942495, < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13; >= 054a3ef683a176a509cc9b37f762029aae942495, < e904961332801c87355f5d11c65bb433e717c489; >= 054a3ef683a176a509cc9b37f762029aae942495, < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; >= 054a3ef683a176a509cc9b37f762029aae942495, < bcb8889c4981fdde42d4fd2c29a77d510fe21da2 |
| Linux | Linux | 6.2 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64377?
How severe is CVE-2026-64377?
How do I fix CVE-2026-64377?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64371In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64372In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64373In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64374In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64375In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64376In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64378In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64379In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64380In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-64381In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64382In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64383In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-64377?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
