Skip to main content
VulnerabilityPublished Updated

CVE-2026-64377: Linux kernel · cpufreq: qcom-cpufreq-hw: Fix possible double free

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e904961332801c87355f5d11c65bb433e717c489 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e904961332801c87355f5d11c65bb433e717c489, bcb8889c4981fdde42d4fd2c29a77d510fe21da2, 28a03a3f6e6cda0b0da3b43761d175dec5d14d13 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 054a3ef683a176a509cc9b37f762029aae942495, < e904961332801c87355f5d11c65bb433e717c489
Fixed in
  • e904961332801c87355f5d11c65bb433e717c489
LinuxLinuxAffected
  • ≥ 054a3ef683a176a509cc9b37f762029aae942495, < bcb8889c4981fdde42d4fd2c29a77d510fe21da2
Fixed in
  • bcb8889c4981fdde42d4fd2c29a77d510fe21da2
LinuxLinuxAffected
  • ≥ 054a3ef683a176a509cc9b37f762029aae942495, < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13
Fixed in
  • 28a03a3f6e6cda0b0da3b43761d175dec5d14d13
LinuxLinuxAffected
  • ≥ 054a3ef683a176a509cc9b37f762029aae942495, < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
Fixed in
  • 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
LinuxLinuxAffected
  • ≥ 054a3ef683a176a509cc9b37f762029aae942495, < 0f012938f21302c08153589c1aca0283f8d6911d
Fixed in
  • 0f012938f21302c08153589c1aca0283f8d6911d
LinuxLinuxAffected
  • =6.2
Fixed in–

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.

References

Community reviews

Loading reviews…