https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T07:26:11.123892+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-01984 bdu:2025-01984 2026-10-04T07:26:11.870057+00:00 bdu:2025-01984 https://cve.radiocsirt.org/vuln/bell-cve-2023-52923 BELL-CVE-2023-52923 2026-10-04T07:26:11.870131+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0088 certfr-2025-avi-0088 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-04T07:26:11.870167+00:00 certfr-2025-avi-0088 https://cve.radiocsirt.org/vuln/euvd-2026-345101 EUVD-2026-345101 2026-10-04T07:26:11.870192+00:00 EUVD-2026-345101 https://cve.radiocsirt.org/vuln/fkie_cve-2023-52923 fkie_cve-2023-52923 2026-10-04T07:26:11.870204+00:00

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

netfilter: nf_tables: adapt set backend to use GC transaction API

Use the GC transaction API to replace the old and buggy gc API and the busy mark approach.

No set elements are removed from async garbage collection anymore, instead the _DEAD bit is set on so the set element is not visible from lookup path anymore. Async GC enqueues transaction work that might be aborted and retried later.

rbtree and pipapo set backends does not set on the _DEAD bit from the sync GC path since this runs in control plane path where mutex is held. In this case, set elements are deactivated, removed and then released via RCU callback, sync GC never fails.

 https://cve.radiocsirt.org/vuln/ghsa-f2qv-j847-m6vp GHSA-f2qv-j847-m6vp 2026-10-04T07:26:11.870237+00:00

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

netfilter: nf_tables: adapt set backend to use GC transaction API

Use the GC transaction API to replace the old and buggy gc API and the busy mark approach.

No set elements are removed from async garbage collection anymore, instead the _DEAD bit is set on so the set element is not visible from lookup path anymore. Async GC enqueues transaction work that might be aborted and retried later.

rbtree and pipapo set backends does not set on the _DEAD bit from the sync GC path since this runs in control plane path where mutex is held. In this case, set elements are deactivated, removed and then released via RCU callback, sync GC never fails.

 https://cve.radiocsirt.org/vuln/suse-su-2025:02588-1 SUSE-SU-2025:02588-1 — Security update for the Linux Kernel 2026-10-04T07:26:11.870258+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52923 UBUNTU-CVE-2023-52923 2026-10-04T07:26:11.870287+00:00

Affected: 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, Ubuntu:16.04:LTS: linux-hwe-edge and 151 more

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: adapt set backend to use GC transaction API Use the GC transaction API to replace the old and buggy gc API and the busy mark approach. No set elements are removed from async garbage collection anymore, instead the _DEAD bit is set on so the set element is not visible from lookup path anymore. Async GC enqueues transaction work that might be aborted and retried later. rbtree and pipapo set backends does not set on the _DEAD bit from the sync GC path since this runs in control plane path where mutex is held. In this case, set elements are deactivated, removed and then released via RCU callback, sync GC never fails.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0132 WID-SEC-W-2025-0132 — Linux Kernel: Schwachstelle ermöglicht Denial of Service 2026-10-04T07:26:11.870468+00:00

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.