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.
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13 Patch
- git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d Patch
- git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2 Patch
- git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489 Patch
- git.kernel.org/stable/c/0f012938f21302c08153589c1aca0283f8d6911d
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 3 · as of 14 November 2026
- CWE
- CWE-415
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.