https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 19:59:01 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-63822 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-63822 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957 certfr-2026-avi-0957 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957 https://cve.radiocsirt.org/vuln/euvd-2026-353143 EUVD-2026-353143 https://cve.radiocsirt.org/vuln/euvd-2026-353143 https://cve.radiocsirt.org/vuln/fkie_cve-2026-63822 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: ath11k: fix warning when unbinding</p> <p>If there is an error during some initialization related to firmware, the buffers dp-&gt;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 ...</p> <p>The issue is always reproducible from a VM because the MSI addressing initialization is failing.</p> <p>In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: ath11k: fix warning when unbinding</p> <p>If there is an error during some initialization related to firmware, the buffers dp-&gt;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 ...</p> <p>The issue is always reproducible from a VM because the MSI addressing initialization is failing.</p> <p>In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-63822 https://cve.radiocsirt.org/vuln/ghsa-783h-g799-4r2q <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: ath11k: fix warning when unbinding</p> <p>If there is an error during some initialization related to firmware, the buffers dp-&gt;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 ...</p> <p>The issue is always reproducible from a VM because the MSI addressing initialization is failing.</p> <p>In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: ath11k: fix warning when unbinding</p> <p>If there is an error during some initialization related to firmware, the buffers dp-&gt;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 ...</p> <p>The issue is always reproducible from a VM because the MSI addressing initialization is failing.</p> <p>In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.</p> https://cve.radiocsirt.org/vuln/ghsa-783h-g799-4r2q https://cve.radiocsirt.org/vuln/msrc_cve-2026-63822 msrc_CVE-2026-63822 https://cve.radiocsirt.org/vuln/msrc_cve-2026-63822 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1 <p>kernel-devel-7.1.4-1.1 on GA media</p> <p>kernel-devel-7.1.4-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63822 <p><strong>Affected:</strong> 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</p> <p>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-&gt;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.</p> <p><strong>Affected:</strong> 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</p> <p>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-&gt;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63822 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403