https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 11:27:29 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-64377 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-64377 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031 certfr-2026-avi-1031 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031 https://vulnerability.circl.lu/vuln/fkie_cve-2026-64377 <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>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/fkie_cve-2026-64377 https://vulnerability.circl.lu/vuln/ghsa-9gw4-rc8j-j633 <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>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/ghsa-9gw4-rc8j-j633 https://vulnerability.circl.lu/vuln/msrc_cve-2026-64377 msrc_CVE-2026-64377 https://vulnerability.circl.lu/vuln/msrc_cve-2026-64377 https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64377 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more</p> <p>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-&gt;driver_data. 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. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more</p> <p>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-&gt;driver_data. 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. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64377 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527