https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 16:39:56 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64377 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cpufreq: qcom-cpufreq-hw: Fix possible double free</p> <p>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-&gt;driver_data.</p> <p>qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy-&gt;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.</p> <p>Remove the kfree(data) call and let devres release qcom_cpufreq.data.</p> <p>This issue was found by a static analysis tool I am developing.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cpufreq: qcom-cpufreq-hw: Fix possible double free</p> <p>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-&gt;driver_data.</p> <p>qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy-&gt;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.</p> <p>Remove the kfree(data) call and let devres release qcom_cpufreq.data.</p> <p>This issue was found by a static analysis tool I am developing.</p> https://vulnerability.circl.lu/vuln/cve-2026-64377