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
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-07-25 10:17
Updated : 2026-09-08 14:20
NVD link : CVE-2026-64377
Mitre link : CVE-2026-64377
CVE.ORG link : CVE-2026-64377
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-415
Double Free
