- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
Timeline
ID reserved
By Linux
Published
- 17 months later
· 17 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < 27d5d217ae7ffb99dd623375a17a7d3418d9c755
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < 27fda36eedad9e4ec795dc481f307901d1885112
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < 6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < b35de9e01fc79c7baac666fb2dcb4ba7698a1d97
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < 543c0924d446b21f35701ca084d7feca09511220
- affected 5e3dd157d7e70f0e3cea3f2573ed69fb156a19d5 – < 95c38953cb1ecf40399a676a1f85dfe2b5780a9a
- affected 3.11
- unaffected < 3.11
- unaffected 5.10.237 – ≤ 5.10.*
- unaffected 5.15.181 – ≤ 5.15.*
- unaffected 6.1.127 – ≤ 6.1.*
- unaffected 6.6.70 – ≤ 6.6.*
- unaffected 6.12.5 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References8
- https://git.kernel.org/stable/c/27d5d217ae7ffb99dd623375a17a7d3418d9c755 (opens in a new tab)
- https://git.kernel.org/stable/c/27fda36eedad9e4ec795dc481f307901d1885112 (opens in a new tab)
- https://git.kernel.org/stable/c/6e5dbd1c04abf2c19b2282915e6fa48b6ccc6921 (opens in a new tab)
- https://git.kernel.org/stable/c/b35de9e01fc79c7baac666fb2dcb4ba7698a1d97 (opens in a new tab)
- https://git.kernel.org/stable/c/543c0924d446b21f35701ca084d7feca09511220 (opens in a new tab)
- https://git.kernel.org/stable/c/95c38953cb1ecf40399a676a1f85dfe2b5780a9a (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-53247 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-56599)Record last updated .