https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 13:15:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-04669 bdu:2025-04669 https://cve.radiocsirt.org/vuln/bdu:2025-04669 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363 certfr-2024-avi-0363 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363 https://cve.radiocsirt.org/vuln/euvd-2026-309551 EUVD-2026-309551 https://cve.radiocsirt.org/vuln/euvd-2026-309551 https://cve.radiocsirt.org/vuln/fkie_cve-2021-47119 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix memory leak in ext4_fill_super</p> <p>Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked.</p> <p>If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked.</p> <p>This can easily be reproduced by calling an infinite loop of:</p> <p>systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount</p> <p>... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix memory leak in ext4_fill_super</p> <p>Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked.</p> <p>If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked.</p> <p>This can easily be reproduced by calling an infinite loop of:</p> <p>systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount</p> <p>... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-47119 https://cve.radiocsirt.org/vuln/ghsa-xv6r-2m8v-f893 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix memory leak in ext4_fill_super</p> <p>Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked.</p> <p>If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked.</p> <p>This can easily be reproduced by calling an infinite loop of:</p> <p>systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount</p> <p>... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix memory leak in ext4_fill_super</p> <p>Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked.</p> <p>If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked.</p> <p>This can easily be reproduced by calling an infinite loop of:</p> <p>systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount</p> <p>... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> https://cve.radiocsirt.org/vuln/ghsa-xv6r-2m8v-f893 https://cve.radiocsirt.org/vuln/gsd-2021-47119 gsd-2021-47119 https://cve.radiocsirt.org/vuln/gsd-2021-47119 https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47119 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ext4: fix memory leak in ext4_fill_super Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked. If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked. This can easily be reproduced by calling an infinite loop of: systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount ... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ext4: fix memory leak in ext4_fill_super Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked. If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn&#39;t fully free superblock page and buffer head, and being busy, they were not freed and instead leaked. This can easily be reproduced by calling an infinite loop of: systemctl start &lt;ext4_on_lvm&gt;.mount, and systemctl stop &lt;ext4_on_lvm&gt;.mount ... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47119 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652