CVE-2025-23129wifi: ath11k: Clear affinity hint before calling ath11k_pcic_free_irq() in error path
- 5.5MediumCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% 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: ath11k: Clear affinity hint before calling ath11k_pcic_free_irq() in error path If a shared IRQ is used by the driver due to platform limitation, then the IRQ affinity hint is set right after the allocation of IRQ vectors in ath11k_pci_alloc_msi(). This does no harm unless one of the functions requesting the IRQ fails and attempt to free the IRQ. This results in the below warning: WARNING: CPU: 7 PID: 349 at kernel/irq/manage.c:1929 free_irq+0x278/0x29c Call trace: free_irq+0x278/0x29c ath11k_pcic_free_irq+0x70/0x10c [ath11k] ath11k_pci_probe+0x800/0x820 [ath11k_pci] local_pci_probe+0x40/0xbc The warning is due to not clearing the affinity hint before freeing the IRQs. So to fix this issue, clear the IRQ affinity hint before calling ath11k_pcic_free_irq() in the error path. The affinity will be cleared once again further down the error path due to code organization, but that does no harm. Tested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
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.19% · top 91% of all CVEs (14 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 e01b3400d641cb290742849331f0d22e1202538a – < 8d0519f511d93d675f61d6bfb45ffcc945af4b14
- affected d412d0ef300f28d698648cc7c19147ab413251fe – < 7493b9baf0e54b44caae46715aaa409a84bd9f4b
- affected 39564b475ac5a589e6c22c43a08cbd283c295d2c – < 80dc5a2ce5b75d648e08549617f5c555d07ae43c
- affected 39564b475ac5a589e6c22c43a08cbd283c295d2c – < 3fc42cfcc6e336f25dee79b34e57c4a63cd652a5
- affected 39564b475ac5a589e6c22c43a08cbd283c295d2c – < 68410c5bd381a81bcc92b808e7dc4e6b9ed25d11
- affected 5a9f55efa9333e3edb4826d945cfdd8356f6e269
- affected 6.1.63 – < 6.1.188
- affected 6.6.2 – < 6.6.157
- affected 6.5.12 – < 6.6
- affected 6.7
- unaffected < 6.7
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.59 – ≤ 6.12.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References5
- https://git.kernel.org/stable/c/8d0519f511d93d675f61d6bfb45ffcc945af4b14 (opens in a new tab)
- https://git.kernel.org/stable/c/7493b9baf0e54b44caae46715aaa409a84bd9f4b (opens in a new tab)
- https://git.kernel.org/stable/c/80dc5a2ce5b75d648e08549617f5c555d07ae43c (opens in a new tab)
- https://git.kernel.org/stable/c/3fc42cfcc6e336f25dee79b34e57c4a63cd652a5 (opens in a new tab)
- https://git.kernel.org/stable/c/68410c5bd381a81bcc92b808e7dc4e6b9ed25d11 (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-2025-11168 (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-2025-23129)Record last updated .