https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 13 Oct 2026 05:49:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04887 bdu:2026-04887 https://cve.radiocsirt.org/vuln/bdu:2026-04887 https://cve.radiocsirt.org/vuln/bell-cve-2025-38002 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-38002 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0721 certfr-2025-avi-0721 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0721 https://cve.radiocsirt.org/vuln/euvd-2026-346885 EUVD-2026-346885 https://cve.radiocsirt.org/vuln/euvd-2026-346885 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38002 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo()</p> <p>Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case.</p> <p>This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo()</p> <p>Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case.</p> <p>This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38002 https://cve.radiocsirt.org/vuln/ghsa-p6ff-97p8-xxmr <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo()</p> <p>Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case.</p> <p>This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo()</p> <p>Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case.</p> <p>This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</p> https://cve.radiocsirt.org/vuln/ghsa-p6ff-97p8-xxmr https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38002 <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 77 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo() Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case. This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</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 77 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: io_uring/fdinfo: grab ctx-&gt;uring_lock around io_uring_show_fdinfo() Not everything requires locking in there, which is why the &#39;has_lock&#39; variable exists. But enough does that it&#39;s a bit unwieldy to manage. Wrap the whole thing in a -&gt;uring_lock trylock, and just return with no output if we fail to grab it. The existing trylock() will already have greatly diminished utility/output for the failure case. This fixes an issue with reading the SQE fields, if the ring is being actively resized at the same time.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38002 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1270 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1270