https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 20:42:24 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-98243 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2026-98243 https://cve.radiocsirt.org/vuln/euvd-2026-383355 EUVD-2026-383355 https://cve.radiocsirt.org/vuln/euvd-2026-383355 https://cve.radiocsirt.org/vuln/fkie_cve-2026-98243 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3</p> <p>The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared.</p> <p>The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free.</p> <p>Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string.</p> <p>v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3</p> <p>The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared.</p> <p>The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free.</p> <p>Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string.</p> <p>v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-98243 https://cve.radiocsirt.org/vuln/ghsa-r72r-63qh-x7gr <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3</p> <p>The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared.</p> <p>The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free.</p> <p>Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string.</p> <p>v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3</p> <p>The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared.</p> <p>The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free.</p> <p>Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string.</p> <p>v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</p> https://cve.radiocsirt.org/vuln/ghsa-r72r-63qh-x7gr https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98243 <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 96 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3 The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared. The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free. Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string. v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</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 96 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3 The patch &#34;dma-buf: dma-fence: Fix potential NULL pointer dereference&#34; changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared. The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn&#39;t true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free. Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string. v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98243