https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T21:15:13.721129+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-12336 bdu:2026-12336 2026-10-02T21:15:13.883877+00:00 bdu:2026-12336 https://cve.radiocsirt.org/vuln/bell-cve-2026-23367 BELL-CVE-2026-23367 2026-10-02T21:15:13.883945+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0376 certfr-2026-avi-0376 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu… 2026-10-02T21:15:13.883982+00:00 certfr-2026-avi-0376 https://cve.radiocsirt.org/vuln/euvd-2026-315504 EUVD-2026-315504 2026-10-02T21:15:13.884001+00:00 EUVD-2026-315504 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23367 fkie_cve-2026-23367 2026-10-02T21:15:13.884014+00:00

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

wifi: radiotap: reject radiotap with unknown bits

The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value.

Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present.

 https://cve.radiocsirt.org/vuln/ghsa-mg4x-3g76-43w7 GHSA-mg4x-3g76-43w7 2026-10-02T21:15:13.884048+00:00

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

wifi: radiotap: reject radiotap with unknown bits

The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value.

Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-23367 msrc_CVE-2026-23367 — wifi: radiotap: reject radiotap with unknown bits 2026-10-02T21:15:13.884071+00:00 msrc_CVE-2026-23367 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel 2026-10-02T21:15:13.884089+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:21834-1 SUSE-SU-2026:21834-1 — Security update for the Linux Kernel 2026-10-02T21:15:13.884245+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23367 UBUNTU-CVE-2026-23367 2026-10-02T21:15:13.884380+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: wifi: radiotap: reject radiotap with unknown bits The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value. Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861 WID-SEC-W-2026-0861 — Linux Kernel: Mehrere Schwachstellen 2026-10-02T21:15:13.884692+00:00

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.