https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T14:17:14.926543+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-07331 bdu:2025-07331 2026-10-02T14:17:15.124933+00:00 bdu:2025-07331 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496 certfr-2024-avi-0496 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-02T14:17:15.124994+00:00 certfr-2024-avi-0496 https://cve.radiocsirt.org/vuln/euvd-2026-309614 EUVD-2026-309614 2026-10-02T14:17:15.125016+00:00 EUVD-2026-309614 https://cve.radiocsirt.org/vuln/fkie_cve-2021-47241 fkie_cve-2021-47241 2026-10-02T14:17:15.125029+00:00

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

ethtool: strset: fix message length calculation

Outer nest for ETHTOOL_A_STRSET_STRINGSETS is not accounted for. This may result in ETHTOOL_MSG_STRSET_GET producing a warning like:

calculated message payload length (684) not sufficient WARNING: CPU: 0 PID: 30967 at net/ethtool/netlink.c:369 ethnl_default_doit+0x87a/0xa20

and a splat.

As usually with such warnings three conditions must be met for the warning to trigger: - there must be no skb size rounding up (e.g. reply_size of 684); - string set must be per-device (so that the header gets populated); - the device name must be at least 12 characters long.

all in all with current user space it looks like reading priv flags is the only place this could potentially happen. Or with syzbot :)

 https://cve.radiocsirt.org/vuln/ghsa-hh94-frj2-pf9r GHSA-hh94-frj2-pf9r 2026-10-02T14:17:15.125070+00:00

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

ethtool: strset: fix message length calculation

Outer nest for ETHTOOL_A_STRSET_STRINGSETS is not accounted for. This may result in ETHTOOL_MSG_STRSET_GET producing a warning like:

calculated message payload length (684) not sufficient WARNING: CPU: 0 PID: 30967 at net/ethtool/netlink.c:369 ethnl_default_doit+0x87a/0xa20

and a splat.

As usually with such warnings three conditions must be met for the warning to trigger: - there must be no skb size rounding up (e.g. reply_size of 684); - string set must be per-device (so that the header gets populated); - the device name must be at least 12 characters long.

all in all with current user space it looks like reading priv flags is the only place this could potentially happen. Or with syzbot :)

 https://cve.radiocsirt.org/vuln/gsd-2021-47241 gsd-2021-47241 2026-10-02T14:17:15.125094+00:00 gsd-2021-47241 https://cve.radiocsirt.org/vuln/suse-su-2024:2010-1 SUSE-SU-2024:2010-1 — Security update for the Linux Kernel 2026-10-02T14:17:15.125104+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47241 UBUNTU-CVE-2021-47241 2026-10-02T14:17:15.125227+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 54 more

In the Linux kernel, the following vulnerability has been resolved: ethtool: strset: fix message length calculation Outer nest for ETHTOOL_A_STRSET_STRINGSETS is not accounted for. This may result in ETHTOOL_MSG_STRSET_GET producing a warning like: calculated message payload length (684) not sufficient WARNING: CPU: 0 PID: 30967 at net/ethtool/netlink.c:369 ethnl_default_doit+0x87a/0xa20 and a splat. As usually with such warnings three conditions must be met for the warning to trigger: - there must be no skb size rounding up (e.g. reply_size of 684); - string set must be per-device (so that the header gets populated); - the device name must be at least 12 characters long. all in all with current user space it looks like reading priv flags is the only place this could potentially happen. Or with syzbot :)