Vulnerability · Published Dec 27, 2024 · Assigned by Linux
CVE-2024-56599wifi: ath10k: avoid NULL pointer error during sdio remove
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 14% 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: ath10k: avoid NULL pointer error during sdio remove When running 'rmmod ath10k', ath10k_sdio_remove() will free sdio workqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON is set to yes, kernel panic will happen: Call trace: destroy_workqueue+0x1c/0x258 ath10k_sdio_remove+0x84/0x94 sdio_bus_remove+0x50/0x16c device_release_driver_internal+0x188/0x25c device_driver_detach+0x20/0x2c This is because during 'rmmod ath10k', ath10k_sdio_remove() will call ath10k_core_destroy() before destroy_workqueue(). wiphy_dev_release() will finally be called in ath10k_core_destroy(). This function will free struct cfg80211_registered_device *rdev and all its members, including wiphy, dev and the pointer of sdio workqueue. Then the pointer of sdio workqueue will be set to NULL due to CONFIG_INIT_ON_FREE_DEFAULT_ON. After device release, destroy_workqueue() will use NULL pointer then the kernel panic happen. Call trace: ath10k_sdio_remove ->ath10k_core_unregister …… ->ath10k_core_stop ->ath10k_hif_stop ->ath10k_sdio_irq_disable ->ath10k_hif_power_down ->del_timer_sync(&ar_sdio->sleep_timer) ->ath10k_core_destroy ->ath10k_mac_destroy ->ieee80211_free_hw ->wiphy_free …… ->wiphy_dev_release ->destroy_workqueue Need to call destroy_workqueue() before ath10k_core_destroy(), free the work queue buffer first and then free pointer of work queue by ath10k_core_destroy(). This order matches the error path order in ath10k_sdio_probe(). No work will be queued on sdio workqueue between it is destroyed and ath10k_core_destroy() is called. Based on the call_stack above, the reason is: Only ath10k_sdio_sleep_timer_handler(), ath10k_sdio_hif_tx_sg() and ath10k_sdio_irq_disable() will queue work on sdio workqueue. Sleep timer will be deleted before ath10k_core_destroy() in ath10k_hif_power_down(). ath10k_sdio_irq_disable() only be called in ath10k_hif_stop(). ath10k_core_unregister() will call ath10k_hif_power_down() to stop hif bus, so ath10k_sdio_hif_tx_sg() won't be called anymore. Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00189
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.128-1 | DEBIAN-CVE-2024-56599 |
| Debian:12 | linux | 6.1.128-1 | DSA-5860-1 |
| Debian:13 | linux | 6.12.5-1 | DEBIAN-CVE-2024-56599 |
| Debian:14 | linux | 6.12.5-1 | DEBIAN-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux | 5.15.0-140.150 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux | 5.15.0-140.150 | USN-7510-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-58.60 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1084.91 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1084.91 | USN-7510-7 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1027.29 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1027.29~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1089.98 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1089.98 | USN-7510-3 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1027.32 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1012.12~24.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1027.32~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1089.98.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1014.15 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1083.92 | USN-7511-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1083.92 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1028.30 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1011.11~24.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1028.30~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1081.87 | USN-7511-3 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1081.87 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1023.27 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1066.74 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1066.74 | USN-7510-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1010.12 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-21.21~24.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-58.60~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1076.79 | USN-7510-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1076.79 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1024.24 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1024.24~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1079.85 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1079.85 | USN-7510-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1080.85 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1080.85 | USN-7510-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-140.150 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-140.150 | USN-7510-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-58.60.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-58.60.1~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1078.79 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1078.79 | USN-7510-1 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1026.29 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1007.7 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1026.29~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1026.29.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1037.37 | USN-7510-3 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1037.37 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1008.8 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1026.26 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1026.26 | USN-7510-7 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1017.17 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1026.26 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1081.87 | USN-7510-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1081.87 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1024.25 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1024.25~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1078.81 | USN-7510-7 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1078.81 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1028.32 | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-58.60.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-58.60.1~22.04.1 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-56599 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1017.18 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1050.54 | UBUNTU-CVE-2024-56599 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1050.54 | USN-7602-1 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before 27d5d217ae7ffb99dd623375a17a7d3418d9c7555e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before 27fda36eedad9e4ec795dc481f307901d18851125e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before 6e5dbd1c04abf2c19b2282915e6fa48b6ccc69215e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before b35de9e01fc79c7baac666fb2dcb4ba7698a1d975e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before 543c0924d446b21f35701ca084d7feca095112205e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – before 95c38953cb1ecf40399a676a1f85dfe2b5780a9a |
| Linux | Linux | 3.11 |
References
- https://git.kernel.org/stable/c/27d5d217ae7ffb99dd623375a17a7d3418d9c755
- https://git.kernel.org/stable/c/27fda36eedad9e4ec795dc481f307901d1885112
- https://git.kernel.org/stable/c/6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921
- https://git.kernel.org/stable/c/b35de9e01fc79c7baac666fb2dcb4ba7698a1d97
- https://git.kernel.org/stable/c/543c0924d446b21f35701ca084d7feca09511220
- https://git.kernel.org/stable/c/95c38953cb1ecf40399a676a1f85dfe2b5780a9a
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html