https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T10:08:14.133525+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-13783 bdu:2025-13783 2026-10-03T10:08:14.157621+00:00 bdu:2025-13783 https://cve.radiocsirt.org/vuln/bell-cve-2025-40067 BELL-CVE-2025-40067 2026-10-03T10:08:14.157665+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0169 certfr-2026-avi-0169 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a… 2026-10-03T10:08:14.157695+00:00 certfr-2026-avi-0169 https://cve.radiocsirt.org/vuln/euvd-2026-347323 EUVD-2026-347323 2026-10-03T10:08:14.157713+00:00 EUVD-2026-347323 https://cve.radiocsirt.org/vuln/fkie_cve-2025-40067 fkie_cve-2025-40067 2026-10-03T10:08:14.157724+00:00

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist

Index allocation requires at least one bit in the $BITMAP attribute to track usage of index entries. If the bitmap is empty while index blocks are already present, this reflects on-disk corruption.

syzbot triggered this condition using a malformed NTFS image. During a rename() operation involving a long filename (which spans multiple index entries), the empty bitmap allowed the name to be added without valid tracking. Subsequent deletion of the original entry failed with -ENOENT, due to unexpected index state.

Reject such cases by verifying that the bitmap is not empty when index blocks exist.

 https://cve.radiocsirt.org/vuln/ghsa-rxpf-8w5h-7fch GHSA-rxpf-8w5h-7fch 2026-10-03T10:08:14.157755+00:00

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist

Index allocation requires at least one bit in the $BITMAP attribute to track usage of index entries. If the bitmap is empty while index blocks are already present, this reflects on-disk corruption.

syzbot triggered this condition using a malformed NTFS image. During a rename() operation involving a long filename (which spans multiple index entries), the empty bitmap allowed the name to be added without valid tracking. Subsequent deletion of the original entry failed with -ENOENT, due to unexpected index state.

Reject such cases by verifying that the bitmap is not empty when index blocks exist.

 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15702-1 openSUSE-SU-2025:15702-1 — kernel-devel-6.17.7-1.1 on GA media 2026-10-03T10:08:14.157776+00:00

kernel-devel-6.17.7-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40067 UBUNTU-CVE-2025-40067 2026-10-03T10:08:14.157837+00:00

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

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist Index allocation requires at least one bit in the $BITMAP attribute to track usage of index entries. If the bitmap is empty while index blocks are already present, this reflects on-disk corruption. syzbot triggered this condition using a malformed NTFS image. During a rename() operation involving a long filename (which spans multiple index entries), the empty bitmap allowed the name to be added without valid tracking. Subsequent deletion of the original entry failed with -ENOENT, due to unexpected index state. Reject such cases by verifying that the bitmap is not empty when index blocks exist.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2431 WID-SEC-W-2025-2431 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T10:08:14.157987+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um beliebigen Code auszuführen, privilegierten Zugriff zu erlangen, sensible Informationen zu stehlen oder betroffene Systeme funktionsunfähig zu machen.