Vulnerability · Published Jun 18, 2025 · Assigned by Linux
CVE-2025-38009wifi: mt76: disable napi on driver removal
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: disable napi on driver removal A warning on driver removal started occurring after commit 9dd05df8403b ("net: warn if NAPI instance wasn't shut down"). Disable tx napi before deleting it in mt76_dma_cleanup(). WARNING: CPU: 4 PID: 18828 at net/core/dev.c:7288 __netif_napi_del_locked+0xf0/0x100 CPU: 4 UID: 0 PID: 18828 Comm: modprobe Not tainted 6.15.0-rc4 #4 PREEMPT(lazy) Hardware name: ASUS System Product Name/PRIME X670E-PRO WIFI, BIOS 3035 09/05/2024 RIP: 0010:__netif_napi_del_locked+0xf0/0x100 Call Trace: <TASK> mt76_dma_cleanup+0x54/0x2f0 [mt76] mt7921_pci_remove+0xd5/0x190 [mt7921e] pci_device_remove+0x47/0xc0 device_release_driver_internal+0x19e/0x200 driver_detach+0x48/0x90 bus_remove_driver+0x6d/0xf0 pci_unregister_driver+0x2e/0xb0 __do_sys_delete_module.isra.0+0x197/0x2e0 do_syscall_64+0x7b/0x160 entry_SYSCALL_64_after_hwframe+0x76/0x7e Tested with mt7921e but the same pattern can be actually applied to other mt76 drivers calling mt76_dma_cleanup() during removal. Tx napi is enabled in their *_dma_init() functions and only toggled off and on again inside their suspend/resume/reset paths. So it should be okay to disable tx napi in such a generic way. Found by Linux Verification Center (linuxtesting.org).
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.140-1 | DEBIAN-CVE-2025-38009 |
| Debian:13 | linux | 6.12.30-1 | DEBIAN-CVE-2025-38009 |
| Debian:14 | linux | 6.12.30-1 | DEBIAN-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux | 5.15.0-144.157 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux | 6.8.0-100.100 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1088.95 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1046.49 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | 6.14.0-1011.11~24.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | 6.14.0-1011.11~24.04.1 | USN-7699-1 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1046.49~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1094.103 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1046.52 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1051.57~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1094.103.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1046.53 | UBUNTU-CVE-2025-38009 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1046.53~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1087.96 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1047.50 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | 6.14.0-1014.15~24.04.1 | USN-7699-1 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | 6.14.0-1014.15~24.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1047.50~22.04.2 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1085.91 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1043.48 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1070.78 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1030.33 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | 6.14.0-28.28~24.04.1 | USN-7699-2 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-100.100~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1080.83 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1044.44 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1044.44~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1083.89 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1084.89 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-144.157 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-100.100.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-100.100.1~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1082.83 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1046.49 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1046.49~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1046.49.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1041.41 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1020.20 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1030.30 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | 6.14.0-1010.10 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | 6.14.0-1010.10 | USN-7699-2 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1085.91 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1043.44 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | 6.14.0-1011.11~24.04.1 | USN-7699-1 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | 6.14.0-1011.11~24.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1043.44~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1083.86 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1047.51 | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | 6.14.0-28.28.1~24.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-100.100~22.04.1 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-38009 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1023.24 | UBUNTU-CVE-2025-38009 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1052.56 | UBUNTU-CVE-2025-38009 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2ac515a5d74f26963362d5da9589c67ca3663338 – before ff0f820fa5b99035b3c654dd531226d8d83aec5f2ac515a5d74f26963362d5da9589c67ca3663338 – before ca5b213bf4b4224335a8131a26805d16503fca5f2ac515a5d74f26963362d5da9589c67ca3663338 – before b892e830d1ea8c5475254b98827771f7366f10392ac515a5d74f26963362d5da9589c67ca3663338 – before 5e700b06b970fc19e3a1ecb244e14785f3fbb8e32ac515a5d74f26963362d5da9589c67ca3663338 – before 2b81e76db3667d1f7f2ad44e9835cdaf8dea95a82ac515a5d74f26963362d5da9589c67ca3663338 – before e7bfbda5fddd27f3158e723d641c0fcdfb0552a72ac515a5d74f26963362d5da9589c67ca3663338 – before 78ab4be549533432d97ea8989d2f00b508fa68d8 |
| Linux | Linux | 5.2 |
References
- https://git.kernel.org/stable/c/ff0f820fa5b99035b3c654dd531226d8d83aec5f
- https://git.kernel.org/stable/c/ca5b213bf4b4224335a8131a26805d16503fca5f
- https://git.kernel.org/stable/c/b892e830d1ea8c5475254b98827771f7366f1039
- https://git.kernel.org/stable/c/5e700b06b970fc19e3a1ecb244e14785f3fbb8e3
- https://git.kernel.org/stable/c/2b81e76db3667d1f7f2ad44e9835cdaf8dea95a8
- https://git.kernel.org/stable/c/e7bfbda5fddd27f3158e723d641c0fcdfb0552a7
- https://git.kernel.org/stable/c/78ab4be549533432d97ea8989d2f00b508fa68d8
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html