https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 22:18:01 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-53139 <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-2026-53139 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/euvd-2026-332511 EUVD-2026-332511 https://cve.radiocsirt.org/vuln/euvd-2026-332511 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53139 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/v3d: Skip CSD when it has zeroed workgroups</p> <p>A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op.</p> <p>These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op.</p> <p>Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/v3d: Skip CSD when it has zeroed workgroups</p> <p>A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op.</p> <p>These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op.</p> <p>Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-53139 https://cve.radiocsirt.org/vuln/ghsa-qcxp-rj5j-4rr9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/v3d: Skip CSD when it has zeroed workgroups</p> <p>A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op.</p> <p>These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op.</p> <p>Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/v3d: Skip CSD when it has zeroed workgroups</p> <p>A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op.</p> <p>These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op.</p> <p>Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</p> https://cve.radiocsirt.org/vuln/ghsa-qcxp-rj5j-4rr9 https://cve.radiocsirt.org/vuln/msrc_cve-2026-53139 msrc_CVE-2026-53139 https://cve.radiocsirt.org/vuln/msrc_cve-2026-53139 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1 https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53139 <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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 228 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Skip CSD when it has zeroed workgroups A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op. These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op. Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 228 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Skip CSD when it has zeroed workgroups A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op. These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op. Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don&#39;t submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53139 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077 <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077