https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T06:24:20.293817+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-43092 BELL-CVE-2026-43092 2026-10-03T06:24:20.546257+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a… 2026-10-03T06:24:20.546335+00:00 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-315745 EUVD-2026-315745 2026-10-03T06:24:20.546357+00:00 EUVD-2026-315745 https://cve.radiocsirt.org/vuln/fkie_cve-2026-43092 fkie_cve-2026-43092 2026-10-03T06:24:20.546370+00:00

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

xsk: validate MTU against usable frame size on bind

AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk.

This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).

 https://cve.radiocsirt.org/vuln/ghsa-gpc7-hgpf-xq94 GHSA-gpc7-hgpf-xq94 2026-10-03T06:24:20.546403+00:00

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

xsk: validate MTU against usable frame size on bind

AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk.

This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1 openSUSE-SU-2026:21388-1 — Security update for the Linux Kernel 2026-10-03T06:24:20.546425+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1 SUSE-SU-2026:22742-1 — Security update for the Linux Kernel 2026-10-03T06:24:20.546583+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43092 UBUNTU-CVE-2026-43092 2026-10-03T06:24:20.546738+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 141 more

In the Linux kernel, the following vulnerability has been resolved: xsk: validate MTU against usable frame size on bind AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk. This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385 WID-SEC-W-2026-1385 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T06:24:20.546936+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.