CVE-2025-23129

wifi: ath11k: Clear affinity hint before calling ath11k_pcic_free_irq() in error path

MEDIUM
5.5
CVSS Score
Published: April 16, 2025 at 02:13 PM UTC
Updated: September 14, 2026 at 12:34 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.5.126.1.63 ≤ v < 6.1.1886.1.63 ≤ v < 6.26.5.12 ≤ v < 6.66.6.2 ≤ v < 6.14.26.6.2 ≤ v < 6.6.1576.7 ≤ v < 6.12.596.7 ≤ v < 6.14.26.7 ≤ v < 6.1539564b475ac5a589e6c22c43a08cbd283c295d2c5a9f55efa9333e3edb4826d945cfdd8356f6e2696.1.636.5.126.6.26.7d412d0ef300f28d698648cc7c19147ab413251fee01b3400d641cb290742849331f0d22e1202538a
Vendor states this is fixed in 3fc42cfcc6e336f25dee79b34e57c4a63cd652a5 (fixed)
Vendor states this is fixed in 68410c5bd381a81bcc92b808e7dc4e6b9ed25d11 (fixed)
Vendor states this is fixed in 7493b9baf0e54b44caae46715aaa409a84bd9f4b (fixed)
Vendor states this is fixed in 80dc5a2ce5b75d648e08549617f5c555d07ae43c (fixed)
Vendor states this is fixed in 8d0519f511d93d675f61d6bfb45ffcc945af4b14 (fixed)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.59 (unaffected)
Vendor states this is fixed in 6.14.2 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card