https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T23:42:36.633510+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-00742 bdu:2026-00742 2026-10-03T23:42:36.697792+00:00 bdu:2026-00742 https://cve.radiocsirt.org/vuln/bell-cve-2025-68767 BELL-CVE-2025-68767 2026-10-03T23:42:36.697860+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166 certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo… 2026-10-03T23:42:36.697897+00:00 certfr-2026-avi-0166 https://cve.radiocsirt.org/vuln/euvd-2026-315175 EUVD-2026-315175 2026-10-03T23:42:36.697916+00:00 EUVD-2026-315175 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68767 fkie_cve-2025-68767 2026-10-03T23:42:36.697928+00:00

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

hfsplus: Verify inode mode when loading from disk

syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when the S_IFMT bits of the 16bits "mode" field loaded from disk are corrupted.

According to [1], the permissions field was treated as reserved in Mac OS 8 and 9. According to [2], the reserved field was explicitly initialized with 0, and that field must remain 0 as long as reserved. Therefore, when the "mode" field is not 0 (i.e. no longer reserved), the file must be S_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/ S_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.

 https://cve.radiocsirt.org/vuln/ghsa-mgmc-76vj-qf3j GHSA-mgmc-76vj-qf3j 2026-10-03T23:42:36.697963+00:00

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

hfsplus: Verify inode mode when loading from disk

syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when the S_IFMT bits of the 16bits "mode" field loaded from disk are corrupted.

According to [1], the permissions field was treated as reserved in Mac OS 8 and 9. According to [2], the reserved field was explicitly initialized with 0, and that field must remain 0 as long as reserved. Therefore, when the "mode" field is not 0 (i.e. no longer reserved), the file must be S_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/ S_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.

 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68767 msrc_CVE-2025-68767 — hfsplus: Verify inode mode when loading from disk 2026-10-03T23:42:36.697985+00:00 msrc_CVE-2025-68767 https://cve.radiocsirt.org/vuln/suse-su-2026:0473-1 SUSE-SU-2026:0473-1 — Security update for the Linux Kernel 2026-10-03T23:42:36.698001+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68767 UBUNTU-CVE-2025-68767 2026-10-03T23:42:36.698125+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: hfsplus: Verify inode mode when loading from disk syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when the S_IFMT bits of the 16bits "mode" field loaded from disk are corrupted. According to [1], the permissions field was treated as reserved in Mac OS 8 and 9. According to [2], the reserved field was explicitly initialized with 0, and that field must remain 0 as long as reserved. Therefore, when the "mode" field is not 0 (i.e. no longer reserved), the file must be S_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/ S_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0086 WID-SEC-W-2026-0086 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T23:42:36.698455+00:00

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.