Linux Kernel up to 6.12.95/6.18.38/7.1.3 qcom-cpufreq-hw qcom_cpufreq_hw_cpu_exit double free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k2.32-

Summaryinfo

A vulnerability identified as very critical has been detected in Linux Kernel up to 6.12.95/6.18.38/7.1.3. Affected by this issue is the function qcom_cpufreq_hw_cpu_exit of the component qcom-cpufreq-hw. Performing a manipulation results in double free. This vulnerability is known as CVE-2026-64377. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.12.95/6.18.38/7.1.3. This affects the function qcom_cpufreq_hw_cpu_exit of the component qcom-cpufreq-hw. The manipulation with an unknown input leads to a double free vulnerability. CWE is classifying the issue as CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64377 since 07/19/2026. The exploitability is told to be easy. Attacking locally is a requirement. The exploitation requires an enhanced level of successful authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/25/2026).

Upgrading to version 6.12.96, 6.18.39, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch 28a03a3f6e6cda0b0da3b43761d175dec5d14d13/e904961332801c87355f5d11c65bb433e717c489/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d/bcb8889c4981fdde42d4fd2c29a77d510fe21da2 is able to eliminate this problem.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.8

VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Double free
CWE: CWE-415 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.96/6.18.39/7.1.4/7.2-rc1
Patch: 28a03a3f6e6cda0b0da3b43761d175dec5d14d13/e904961332801c87355f5d11c65bb433e717c489/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d/bcb8889c4981fdde42d4fd2c29a77d510fe21da2

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64377 (🔒)
GCVE (CVE): GCVE-0-2026-64377
GCVE (VulDB): GCVE-100-383175

Entryinfo

Created: 07/25/2026 18:01
Changes: 07/25/2026 18:01 (59)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!