Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 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

CVSS scores of CVE-2026-64377, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS: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)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 054a3ef683a176a509cc9b37f762029aae942495 – < 0f012938f21302c08153589c1aca0283f8d6911d
    • affected 054a3ef683a176a509cc9b37f762029aae942495 – < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13
    • affected 054a3ef683a176a509cc9b37f762029aae942495 – < e904961332801c87355f5d11c65bb433e717c489
    • affected 054a3ef683a176a509cc9b37f762029aae942495 – < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
    • affected 054a3ef683a176a509cc9b37f762029aae942495 – < bcb8889c4981fdde42d4fd2c29a77d510fe21da2
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64377 badge
[![CVE-2026-64377](https://cveledger.app/badge/CVE-2026-64377.svg)](https://cveledger.app/cve/CVE-2026-64377)

Record last updated .