CVE-2025-23129None▾ SunlitIn 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 af…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 14.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
5.5 → —
medium → none
0.2% → 0.2%
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
Linux >= e01b3400d641cb290742849331f0d22e1202538a < 8d0519f511d93d675f61d6bfb45ffcc945af4b14Linux >= d412d0ef300f28d698648cc7c19147ab413251fe < 7493b9baf0e54b44caae46715aaa409a84bd9f4bLinux >= 39564b475ac5a589e6c22c43a08cbd283c295d2c < 80dc5a2ce5b75d648e08549617f5c555d07ae43cLinux >= 39564b475ac5a589e6c22c43a08cbd283c295d2c < 3fc42cfcc6e336f25dee79b34e57c4a63cd652a5Linux >= 39564b475ac5a589e6c22c43a08cbd283c295d2c < 68410c5bd381a81bcc92b808e7dc4e6b9ed25d11Linux 5a9f55efa9333e3edb4826d945cfdd8356f6e269Linux >= 6.1.63 < 6.1.188Linux >= 6.6.2 < 6.6.157Linux >= 6.5.12 < 6.6Linux 6.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets