https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T22:05:12.160590+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-63822 BELL-CVE-2026-63822 2026-10-03T22:05:12.958087+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957 certfr-2026-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à… 2026-10-03T22:05:12.958202+00:00 certfr-2026-avi-0957 https://cve.radiocsirt.org/vuln/euvd-2026-353143 EUVD-2026-353143 2026-10-03T22:05:12.958237+00:00 EUVD-2026-353143 https://cve.radiocsirt.org/vuln/fkie_cve-2026-63822 fkie_cve-2026-63822 2026-10-03T22:05:12.958263+00:00

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

wifi: ath11k: fix warning when unbinding

If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath11k_pci), and we get: WARNING: CPU: 0 PID: 6231 at mm/slub.c:4368 free_large_kmalloc+0x57/0x90 Call Trace: free_large_kmalloc ath11k_dp_free ath11k_core_deinit ath11k_pci_remove ...

The issue is always reproducible from a VM because the MSI addressing initialization is failing.

In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.

 https://cve.radiocsirt.org/vuln/ghsa-783h-g799-4r2q GHSA-783h-g799-4r2q 2026-10-03T22:05:12.958328+00:00

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

wifi: ath11k: fix warning when unbinding

If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath11k_pci), and we get: WARNING: CPU: 0 PID: 6231 at mm/slub.c:4368 free_large_kmalloc+0x57/0x90 Call Trace: free_large_kmalloc ath11k_dp_free ath11k_core_deinit ath11k_pci_remove ...

The issue is always reproducible from a VM because the MSI addressing initialization is failing.

In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-63822 msrc_CVE-2026-63822 — wifi: ath11k: fix warning when unbinding 2026-10-03T22:05:12.958385+00:00 msrc_CVE-2026-63822 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1 openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media 2026-10-03T22:05:12.958418+00:00

kernel-devel-7.1.4-1.1 on GA media

 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 SUSE-SU-2026:23066-1 — Security update for the Linux Kernel 2026-10-03T22:05:12.958496+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63822 UBUNTU-CVE-2026-63822 2026-10-03T22:05:12.959150+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 193 more

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix warning when unbinding If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath11k_pci), and we get: WARNING: CPU: 0 PID: 6231 at mm/slub.c:4368 free_large_kmalloc+0x57/0x90 Call Trace: free_large_kmalloc ath11k_dp_free ath11k_core_deinit ath11k_pci_remove ... The issue is always reproducible from a VM because the MSI addressing initialization is failing. In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff 2026-10-03T22:05:12.959560+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.