CVE-2026-64377cpufreq: qcom-cpufreq-hw: Fix possible double free
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 054a3ef683a176a509cc9b37f762029aae942495 – < 0f012938f21302c08153589c1aca0283f8d6911d
- affected 054a3ef683a176a509cc9b37f762029aae942495 – < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13
- affected 054a3ef683a176a509cc9b37f762029aae942495 – < e904961332801c87355f5d11c65bb433e717c489
- affected 054a3ef683a176a509cc9b37f762029aae942495 – < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
- affected 054a3ef683a176a509cc9b37f762029aae942495 – < bcb8889c4981fdde42d4fd2c29a77d510fe21da2
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0f012938f21302c08153589c1aca0283f8d6911d (opens in a new tab)
- https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13 (opens in a new tab)
- https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489 (opens in a new tab)
- https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d (opens in a new tab)
- https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48921 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64377)Record last updated .