https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 16:03:37 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15072 bdu:2025-15072 https://cve.radiocsirt.org/vuln/bdu:2025-15072 https://cve.radiocsirt.org/vuln/bell-cve-2024-53075 <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://cve.radiocsirt.org/vuln/bell-cve-2024-53075 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/euvd-2026-313601 EUVD-2026-313601 https://cve.radiocsirt.org/vuln/euvd-2026-313601 https://cve.radiocsirt.org/vuln/fkie_cve-2024-53075 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Prevent a bad reference count on CPU nodes</p> <p>When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired.</p> <p>Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node.</p> <p>Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Prevent a bad reference count on CPU nodes</p> <p>When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired.</p> <p>Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node.</p> <p>Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-53075 https://cve.radiocsirt.org/vuln/ghsa-7866-w9g3-g699 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Prevent a bad reference count on CPU nodes</p> <p>When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired.</p> <p>Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node.</p> <p>Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Prevent a bad reference count on CPU nodes</p> <p>When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired.</p> <p>Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node.</p> <p>Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</p> https://cve.radiocsirt.org/vuln/ghsa-7866-w9g3-g699 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53075 <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 69 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: riscv: Prevent a bad reference count on CPU nodes When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired. Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node. Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</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 69 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: riscv: Prevent a bad reference count on CPU nodes When populating cache leaves we previously fetched the CPU device node at the very beginning. But when ACPI is enabled we go through a specific branch which returns early and does not call &#39;of_node_put&#39; for the node that was acquired. Since we are not using a CPU device node for the ACPI code anyways, we can simply move the initialization of it just passed the ACPI block, and we are guaranteed to have an &#39;of_node_put&#39; call for the acquired node. This prevents a bad reference count of the CPU device node. Moreover, the previous function did not check for errors when acquiring the device node, so a return -ENOENT has been added for that case.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53075 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509