CVE-2026-63822 — wifi: ath11k: fix warning when unbinding
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ d5c65159f2895379e11ca13f62feabe93278985d and < e569a5cb401a267168621aa9a1e7f07fcc9612c3≥ d5c65159f2895379e11ca13f62feabe93278985d and < 0aa097a370277deab5337030b9e2d395742f469c≥ d5c65159f2895379e11ca13f62feabe93278985d and < 0a946abb82f29abe9a15173b707a449cb039b43e≥ d5c65159f2895379e11ca13f62feabe93278985d and < 318703b6f71d1a29ee0ac46c32a38f7734d4cfb2≥ d5c65159f2895379e11ca13f62feabe93278985d and < 7b2e62b9080bf4a5f4e70cfe47156df8d93a4f13≥ d5c65159f2895379e11ca13f62feabe93278985d and < 40aa3c2b0cb8e34e0576fc94cc70e4e33db03c0a≥ d5c65159f2895379e11ca13f62feabe93278985d and < 051f954b94479d72222c9fbc82a3eef4777bca01≥ d5c65159f2895379e11ca13f62feabe93278985d and < 8b7a26b6681922a38cd5a7829ace61f8e54df9b7 and 1 moreversion 5.6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/e569a5cb401a267168621aa9a1e7f07fcc9612c3
- git.kernel.org/stable/c/0aa097a370277deab5337030b9e2d395742f469c
- git.kernel.org/stable/c/7b2e62b9080bf4a5f4e70cfe47156df8d93a4f13
- git.kernel.org/stable/c/318703b6f71d1a29ee0ac46c32a38f7734d4cfb2
- git.kernel.org/stable/c/40aa3c2b0cb8e34e0576fc94cc70e4e33db03c0a
- git.kernel.org/stable/c/0a946abb82f29abe9a15173b707a449cb039b43e
- git.kernel.org/stable/c/051f954b94479d72222c9fbc82a3eef4777bca01
- git.kernel.org/stable/c/8b7a26b6681922a38cd5a7829ace61f8e54df9b7
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-63822 is "wifi: ath11k: fix warning when unbinding", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.