CVE-2026-63822

wifi: ath11k: fix warning when unbinding

N/A
Published: July 19, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:17 AM 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix warning when unbinding If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath11k_pci), and we get: WARNING: CPU: 0 PID: 6231 at mm/slub.c:4368 free_large_kmalloc+0x57/0x90 Call Trace: free_large_kmalloc ath11k_dp_free ath11k_core_deinit ath11k_pci_remove ... The issue is always reproducible from a VM because the MSI addressing initialization is failing. In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free.

Affected

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

5.6 ≤ v < 5.10.2605.6 ≤ v < 5.15.2115.6 ≤ v < 6.1.1775.6 ≤ v < 6.12.955.6 ≤ v < 6.18.385.6 ≤ v < 6.6.1445.6 ≤ v < 7.1.35.6 ≤ v < 7.25.6d5c65159f2895379e11ca13f62feabe93278985d
Vendor states this is fixed in 051f954b94479d72222c9fbc82a3eef4777bca01 (fixed)
Vendor states this is fixed in 0a946abb82f29abe9a15173b707a449cb039b43e (fixed)
Vendor states this is fixed in 0aa097a370277deab5337030b9e2d395742f469c (fixed)
Vendor states this is fixed in 318703b6f71d1a29ee0ac46c32a38f7734d4cfb2 (fixed)
Vendor states this is fixed in 40aa3c2b0cb8e34e0576fc94cc70e4e33db03c0a (fixed)
Vendor states this is fixed in 7b2e62b9080bf4a5f4e70cfe47156df8d93a4f13 (fixed)
Vendor states this is fixed in 8b7a26b6681922a38cd5a7829ace61f8e54df9b7 (fixed)
Vendor states this is fixed in e569a5cb401a267168621aa9a1e7f07fcc9612c3 (fixed)
Vendor states this is fixed in 5.10.260 (unaffected)
Vendor states this is fixed in 5.15.211 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.177 (unaffected)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusAWAITING ANALYSIS

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