cpufreq: qcom-cpufreq-hw: Fix possible double free
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e904961332801c87355f5d11c65bb433e717c489, Kernel 0f012938f21302c08153589c1aca0283f8d6911d, Kernel 28a03a3f6e6cda0b0da3b43761d175dec5d14d13 and 6 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=054a3ef683a176a509cc9b37f762029aae942495 <e904961332801c87355f5d11c65bb433e717c489, >=054a3ef683a176a509cc9b37f762029aae942495 <0f012938f21302c08153589c1aca0283f8d6911d, >=054a3ef683a176a509cc9b37f762029aae942495 <28a03a3f6e6cda0b0da3b43761d175dec5d14d13, >=054a3ef683a176a509cc9b37f762029aae942495 <9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d, >=054a3ef683a176a509cc9b37f762029aae942495 <bcb8889c4981fdde42d4fd2c29a77d510fe21da2, =6.2 | e904961332801c87355f5d11c65bb433e717c489, 0f012938f21302c08153589c1aca0283f8d6911d, 28a03a3f6e6cda0b0da3b43761d175dec5d14d13, 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d, bcb8889c4981fdde42d4fd2c29a77d510fe21da2 |
| linux-kernel: Kernel | >=6.19.0 <7.1.4, >=6.2.0 <6.6.160, >=6.7.0 <6.12.96, >=6.13.0 <6.18.39 | 7.1.4, 6.6.160, 6.12.96, 6.18.39 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket