https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:07:07 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04208 bdu:2026-04208 https://cve.radiocsirt.org/vuln/bdu:2026-04208 https://cve.radiocsirt.org/vuln/bell-cve-2023-54130 <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-2023-54130 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-345388 EUVD-2026-345388 https://cve.radiocsirt.org/vuln/euvd-2026-345388 https://cve.radiocsirt.org/vuln/fkie_cve-2023-54130 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling</p> <p>Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image.</p> <p>The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO.</p> <p>While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling</p> <p>Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image.</p> <p>The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO.</p> <p>While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-54130 https://cve.radiocsirt.org/vuln/ghsa-2f2v-fxm5-25rj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling</p> <p>Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image.</p> <p>The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO.</p> <p>While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling</p> <p>Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image.</p> <p>The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO.</p> <p>While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</p> https://cve.radiocsirt.org/vuln/ghsa-2f2v-fxm5-25rj https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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:0263-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54130 <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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image. The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO. While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e (&#34;hfs/hfsplus: use WARN_ON for sanity check&#34;) fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image. The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO. While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn&#39;t handled at all (ie neither comment nor subsequent WARN_ON).</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54130 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929 <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929