https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T16:29:33.874090+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-09349 bdu:2024-09349 2026-10-04T16:29:34.148338+00:00 bdu:2024-09349 https://cve.radiocsirt.org/vuln/bell-cve-2024-27050 BELL-CVE-2024-27050 2026-10-04T16:29:34.148396+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0546 certfr-2024-avi-0546 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a… 2026-10-04T16:29:34.148428+00:00 certfr-2024-avi-0546 https://cve.radiocsirt.org/vuln/euvd-2026-345613 EUVD-2026-345613 2026-10-04T16:29:34.148445+00:00 EUVD-2026-345613 https://cve.radiocsirt.org/vuln/fkie_cve-2024-27050 fkie_cve-2024-27050 2026-10-04T16:29:34.148457+00:00

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

libbpf: Use OPTS_SET() macro in bpf_xdp_query()

When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds.

The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.

 https://cve.radiocsirt.org/vuln/ghsa-cw72-f9mw-h9c4 GHSA-cw72-f9mw-h9c4 2026-10-04T16:29:34.148489+00:00

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

libbpf: Use OPTS_SET() macro in bpf_xdp_query()

When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds.

The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.

 https://cve.radiocsirt.org/vuln/gsd-2024-27050 gsd-2024-27050 2026-10-04T16:29:34.148510+00:00 gsd-2024-27050 https://cve.radiocsirt.org/vuln/msrc_cve-2024-27050 msrc_CVE-2024-27050 — libbpf: Use OPTS_SET() macro in bpf_xdp_query() 2026-10-04T16:29:34.148522+00:00 msrc_CVE-2024-27050 https://cve.radiocsirt.org/vuln/oesa-2025-1576 OESA-2025-1576 — libbpf security update 2026-10-04T16:29:34.148537+00:00

Affected: openEuler:24.03-LTS: libbpf

A mirror of bpf-next linux tree bpf-next/tools/lib/bpf directory plus its supporting header files. The version of the package reflects the version of ABI. Security Fix(es):

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

libbpf: Use OPTS_SET() macro in bpf_xdp_query()

When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds.

The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.(CVE-2024-27050)

 https://cve.radiocsirt.org/vuln/suse-su-2024:3194-1 SUSE-SU-2024:3194-1 — Security update for the Linux Kernel 2026-10-04T16:29:34.148566+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27050 UBUNTU-CVE-2024-27050 2026-10-04T16:29:34.148834+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 68 more

In the Linux kernel, the following vulnerability has been resolved: libbpf: Use OPTS_SET() macro in bpf_xdp_query() When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds. The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1008 WID-SEC-W-2024-1008 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service 2026-10-04T16:29:34.148955+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder sonstige Auswirkungen zu verursachen.