https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:59:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13512 bdu:2025-13512 https://cve.radiocsirt.org/vuln/bdu:2025-13512 https://cve.radiocsirt.org/vuln/bell-cve-2025-38377 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-38377 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698 certfr-2025-avi-0698 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698 https://cve.radiocsirt.org/vuln/euvd-2026-347019 EUVD-2026-347019 https://cve.radiocsirt.org/vuln/euvd-2026-347019 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38377 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rose: fix dangling neighbour pointers in rose_rt_device_down()</p> <p>There are two bugs in rose_rt_device_down() that can cause use-after-free:</p> <p>1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries.</p> <p>2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped.</p> <p>For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked.</p> <p>i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false)</p> <p>This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer.</p> <p>Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rose: fix dangling neighbour pointers in rose_rt_device_down()</p> <p>There are two bugs in rose_rt_device_down() that can cause use-after-free:</p> <p>1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries.</p> <p>2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped.</p> <p>For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked.</p> <p>i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false)</p> <p>This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer.</p> <p>Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38377 https://cve.radiocsirt.org/vuln/ghsa-2v78-h87m-hpx9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rose: fix dangling neighbour pointers in rose_rt_device_down()</p> <p>There are two bugs in rose_rt_device_down() that can cause use-after-free:</p> <p>1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries.</p> <p>2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped.</p> <p>For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked.</p> <p>i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false)</p> <p>This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer.</p> <p>Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rose: fix dangling neighbour pointers in rose_rt_device_down()</p> <p>There are two bugs in rose_rt_device_down() that can cause use-after-free:</p> <p>1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries.</p> <p>2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped.</p> <p>For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked.</p> <p>i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false)</p> <p>This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer.</p> <p>Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> https://cve.radiocsirt.org/vuln/ghsa-2v78-h87m-hpx9 https://cve.radiocsirt.org/vuln/msrc_cve-2025-38377 msrc_CVE-2025-38377 https://cve.radiocsirt.org/vuln/msrc_cve-2025-38377 https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38377 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 213 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: rose: fix dangling neighbour pointers in rose_rt_device_down() There are two bugs in rose_rt_device_down() that can cause use-after-free: 1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries. 2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped. For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked. i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false) This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer. Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 213 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: rose: fix dangling neighbour pointers in rose_rt_device_down() There are two bugs in rose_rt_device_down() that can cause use-after-free: 1. The loop bound `t-&gt;count` is modified within the loop, which can cause the loop to terminate early and miss some entries. 2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped. For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked. i=0: (A, A, B) -&gt; (A, B) with count=2 ^ checked i=1: (A, B) -&gt; (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn&#39;t occur because i &lt; count is false) This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer. Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn&#39;t affect subsequent iterations.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38377 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653 <p>Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653