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:13:54 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-11539 bdu:2026-11539 https://cve.radiocsirt.org/vuln/bdu:2026-11539 https://cve.radiocsirt.org/vuln/bell-cve-2025-71292 <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-2025-71292 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696 certfr-2026-avi-0696 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696 https://cve.radiocsirt.org/vuln/euvd-2026-347574 EUVD-2026-347574 https://cve.radiocsirt.org/vuln/euvd-2026-347574 https://cve.radiocsirt.org/vuln/fkie_cve-2025-71292 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>jfs: nlink overflow in jfs_rename</p> <p>If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning.</p> <p>After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>jfs: nlink overflow in jfs_rename</p> <p>If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning.</p> <p>After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-71292 https://cve.radiocsirt.org/vuln/ghsa-469f-r242-gq7h <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>jfs: nlink overflow in jfs_rename</p> <p>If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning.</p> <p>After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>jfs: nlink overflow in jfs_rename</p> <p>If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning.</p> <p>After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</p> https://cve.radiocsirt.org/vuln/ghsa-469f-r242-gq7h https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71292 <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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: jfs: nlink overflow in jfs_rename If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning. After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: jfs: nlink overflow in jfs_rename If nlink is maximal for a directory (-1) and inside that directory you perform a rename for some child directory (not moving from the parent), then the nlink of the first directory is first incremented and later decremented. Normally this is fine, but when nlink = -1 this causes a wrap around to 0, and then drop_nlink issues a warning. After applying the patch syzbot no longer issues any warnings. I also ran some basic fs tests to look for any regressions.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71292 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405