https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T12:02:55.774701+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-11539 bdu:2026-11539 2026-10-03T12:02:55.884790+00:00 bdu:2026-11539 https://cve.radiocsirt.org/vuln/bell-cve-2025-71292 BELL-CVE-2025-71292 2026-10-03T12:02:55.884834+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696 certfr-2026-avi-0696 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à… 2026-10-03T12:02:55.884864+00:00 certfr-2026-avi-0696 https://cve.radiocsirt.org/vuln/euvd-2026-347574 EUVD-2026-347574 2026-10-03T12:02:55.884881+00:00 EUVD-2026-347574 https://cve.radiocsirt.org/vuln/fkie_cve-2025-71292 fkie_cve-2025-71292 2026-10-03T12:02:55.884892+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-469f-r242-gq7h GHSA-469f-r242-gq7h 2026-10-03T12:02:55.884922+00:00

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.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71292 UBUNTU-CVE-2025-71292 2026-10-03T12:02:55.884942+00:00

Affected: 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

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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405 WID-SEC-W-2026-1405 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T12:02:55.885252+00:00

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.