https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T14:57:09.788205+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/alsa-2026:61887 ALSA-2026:61887 — Important: kernel security, bug fix, and enhancement update 2026-10-04T14:57:09.947017+00:00

Affected: AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

* kernel: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834) * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003) * kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454) * kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450) * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970) * kernel: ip6_gre: Use cached t->net in ip6erspan_changelink() (CVE-2026-46120) * kernel: iommu/amd: Fix clone_alias() to use the original device's devid (CVE-2026-53053) * kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026) * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185) * kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196) * kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189) * kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153) * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800) * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397) * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399) * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026…

 https://cve.radiocsirt.org/vuln/bdu:2025-11804 bdu:2025-11804 2026-10-04T14:57:09.947316+00:00 bdu:2025-11804 https://cve.radiocsirt.org/vuln/bell-cve-2025-21834 BELL-CVE-2025-21834 2026-10-04T14:57:09.947338+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254 certfr-2025-avi-0254 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a… 2026-10-04T14:57:09.947359+00:00 certfr-2025-avi-0254 https://cve.radiocsirt.org/vuln/euvd-2026-314059 EUVD-2026-314059 2026-10-04T14:57:09.947374+00:00 EUVD-2026-314059 https://cve.radiocsirt.org/vuln/fkie_cve-2025-21834 fkie_cve-2025-21834 2026-10-04T14:57:09.947385+00:00

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

seccomp: passthrough uretprobe systemcall without filtering

When attaching uretprobes to processes running inside docker, the attached process is segfaulted when encountering the retprobe.

The reason is that now that uretprobe is a system call the default seccomp filters in docker block it as they only allow a specific set of known syscalls. This is true for other userspace applications which use seccomp to control their syscall surface.

Since uretprobe is a "kernel implementation detail" system call which is not used by userspace application code directly, it is impractical and there's very little point in forcing all userspace applications to explicitly allow it in order to avoid crashing tracked processes.

Pass this systemcall through seccomp without depending on configuration.

Note: uretprobe is currently only x86_64 and isn't expected to ever be supported in i386.

[kees: minimized changes for easier backporting, tweaked commit log]

 https://cve.radiocsirt.org/vuln/ghsa-3cmq-72j9-674j GHSA-3cmq-72j9-674j 2026-10-04T14:57:09.947417+00:00

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

seccomp: passthrough uretprobe systemcall without filtering

When attaching uretprobes to processes running inside docker, the attached process is segfaulted when encountering the retprobe.

The reason is that now that uretprobe is a system call the default seccomp filters in docker block it as they only allow a specific set of known syscalls. This is true for other userspace applications which use seccomp to control their syscall surface.

Since uretprobe is a "kernel implementation detail" system call which is not used by userspace application code directly, it is impractical and there's very little point in forcing all userspace applications to explicitly allow it in order to avoid crashing tracked processes.

Pass this systemcall through seccomp without depending on configuration.

Note: uretprobe is currently only x86_64 and isn't expected to ever be supported in i386.

[kees: minimized changes for easier backporting, tweaked commit log]

 https://cve.radiocsirt.org/vuln/rhsa-2026:61887 RHSA-2026:61887 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update 2026-10-04T14:57:09.947441+00:00

kernel: seccomp: passthrough uretprobe systemcall without filtering kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down kernel: ip6_gre: Use cached t->net in ip6erspan_changelink() kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg kernel: iommu/amd: Fix clone_alias() to use the original device's devid kernel: mm/list_lru: drain before clearing xarray entry on reparent kernel: zram: fix use-after-free in zram_bvec_write_partial() kernel: mm/huge_memory: update file PMD counter before folio_put() kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() kernel: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr kernel: NFSv4/flexfiles: reject zero filehandle version count kernel: nfsd: fix posix_acl leak on SETACL decode failure kernel: nfsd: release layout stid on setlease failure kernel: pNFS: Fix use-after-free in pnfs_update_layout() kernel: net: mana: validate rx_req_idx to prevent out-of-bounds array access kernel: smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() kernel: netfilter: ipset: fix race between dump and ip_set_list resize kernel: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count kernel: Input: synaptics-rmi4 - bound the F3A keymap to t…

 https://cve.radiocsirt.org/vuln/rlsa-2026:61887 RLSA-2026:61887 — Important: kernel security, bug fix, and enhancement update 2026-10-04T14:57:09.947515+00:00

Affected: Rocky Linux:10: kernel

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

* kernel: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)

* kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)

* kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)

* kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)

* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)

* kernel: ip6_gre: Use cached t->net in ip6erspan_changelink() (CVE-2026-46120)

* kernel: iommu/amd: Fix clone_alias() to use the original device's devid (CVE-2026-53053)

* kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)

* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)

* kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)

* kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)

* kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)

* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)

* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)

* kernel: NF…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21834 UBUNTU-CVE-2025-21834 2026-10-04T14:57:09.947566+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 71 more

In the Linux kernel, the following vulnerability has been resolved: seccomp: passthrough uretprobe systemcall without filtering When attaching uretprobes to processes running inside docker, the attached process is segfaulted when encountering the retprobe. The reason is that now that uretprobe is a system call the default seccomp filters in docker block it as they only allow a specific set of known syscalls. This is true for other userspace applications which use seccomp to control their syscall surface. Since uretprobe is a "kernel implementation detail" system call which is not used by userspace application code directly, it is impractical and there's very little point in forcing all userspace applications to explicitly allow it in order to avoid crashing tracked processes. Pass this systemcall through seccomp without depending on configuration. Note: uretprobe is currently only x86_64 and isn't expected to ever be supported in i386. [kees: minimized changes for easier backporting, tweaked commit log]

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0499 WID-SEC-W-2025-0499 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T14:57:09.947685+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.