https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 10:26:09 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01160 bdu:2026-01160 https://cve.radiocsirt.org/vuln/bdu:2026-01160 https://cve.radiocsirt.org/vuln/bell-cve-2025-68348 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-68348 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0247 certfr-2026-avi-0247 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0247 https://cve.radiocsirt.org/vuln/euvd-2026-315128 EUVD-2026-315128 https://cve.radiocsirt.org/vuln/euvd-2026-315128 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68348 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix memory leak in __blkdev_issue_zero_pages</p> <p>Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.</p> <p>Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak.</p> <p>This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix memory leak in __blkdev_issue_zero_pages</p> <p>Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.</p> <p>Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak.</p> <p>This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68348 https://cve.radiocsirt.org/vuln/ghsa-9hww-p592-6h89 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix memory leak in __blkdev_issue_zero_pages</p> <p>Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.</p> <p>Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak.</p> <p>This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix memory leak in __blkdev_issue_zero_pages</p> <p>Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.</p> <p>Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak.</p> <p>This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</p> https://cve.radiocsirt.org/vuln/ghsa-9hww-p592-6h89 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1 <p>kernel-devel-6.18.5-1.1 on GA media</p> <p>kernel-devel-6.18.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1 https://cve.radiocsirt.org/vuln/suse-su-2026:20555-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:20555-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68348 <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 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: fix memory leak in __blkdev_issue_zero_pages Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending. Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak. This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</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 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: fix memory leak in __blkdev_issue_zero_pages Move the fatal signal check before bio_alloc() to prevent a memory leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending. Previously, the bio was allocated before checking for a fatal signal. If a signal was pending, the code would break out of the loop without freeing or chaining the just-allocated bio, causing a memory leak. This matches the pattern already used in __blkdev_issue_write_zeroes() where the signal check precedes the allocation.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68348 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2920 <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-2920