https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 03:21:13 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-14410 bdu:2026-14410 https://cve.radiocsirt.org/vuln/bdu:2026-14410 https://cve.radiocsirt.org/vuln/bell-cve-2026-63910 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2026-63910 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-348290 EUVD-2026-348290 https://cve.radiocsirt.org/vuln/euvd-2026-348290 https://cve.radiocsirt.org/vuln/fkie_cve-2026-63910 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf: fix UAF in dma_buf_fd() tracepoint</p> <p>Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free.</p> <p>Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;).</p> <p>This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf: fix UAF in dma_buf_fd() tracepoint</p> <p>Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free.</p> <p>Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;).</p> <p>This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-63910 https://cve.radiocsirt.org/vuln/ghsa-cwcv-9vv2-wx88 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf: fix UAF in dma_buf_fd() tracepoint</p> <p>Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free.</p> <p>Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;).</p> <p>This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf: fix UAF in dma_buf_fd() tracepoint</p> <p>Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free.</p> <p>Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;).</p> <p>This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</p> https://cve.radiocsirt.org/vuln/ghsa-cwcv-9vv2-wx88 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63910 <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 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dma-buf: fix UAF in dma_buf_fd() tracepoint Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free. Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;). This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</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 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dma-buf: fix UAF in dma_buf_fd() tracepoint Once FD_ADD() returns, the fd is live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf-&gt;name_lock -- slab-use-after-free. Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb (&#34;dma-buf: fix UAF in dma_buf_put() tracepoint&#34;). This undoes the FD_ADD() conversion done in commit 34dfce523c90 (&#34;dma: convert dma_buf_fd() to FD_ADD()&#34;); FD_ADD() has no place to hook the tracepoint safely.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63910 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403