CVE-2022-50186: ath11k: fix missing skb drop on htc_tx_completion error
In the Linux kernel, the following vulnerability has been resolved:
ath11k: fix missing skb drop on htc_tx_completion error
On htc_tx_completion error the skb is not dropped. This is wrong since
the completion_handler logic expect the skb to be consumed anyway even
when an error is triggered. Not freeing the skb on error is a memory
leak since the skb won't be freed anywere else. Correctly free the
packet on eid >= ATH11K_HTC_EP_COUNT before returning.
Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
Security readout for executives and security teams
Plain-English summary
CVE-2022-50186 is a Linux kernel memory-leak issue in the ath11k wireless driver. When a transmit completion error occurs, a network packet buffer may not be freed. The direct business risk is potential availability impact on systems using affected ath11k wireless hardware, but the public sources do not provide severity scoring or exploitation evidence.
Executive priority
Handle through normal kernel patch management, with higher priority for devices that rely on ath11k wireless and cannot tolerate availability degradation. Current evidence does not justify emergency treatment without additional vendor or exploitation signals.
Technical view
The resolved flaw is in ath11k htc_tx_completion error handling. The completion handler expects the skb to be consumed even on error, but the code failed to drop it for eid values at or above ATH11K_HTC_EP_COUNT, causing a memory leak. Kernel stable references identify fixes for affected Linux versions.
Likely exposure
Exposure is most likely limited to Linux systems using the ath11k driver for Qualcomm 802.11ax wireless hardware. The source bundle lists Linux kernel versions including 5.17, 5.18.18, 5.19.2, and 6.0 as affected, but vendor backport status must be checked.
Exploitation context
The provided sources do not show active exploitation, public exploit code, KEV listing, CVSS score, or a confirmed remote attack path. Treat this primarily as an availability-oriented kernel defect unless vendor guidance says otherwise.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. No CWE, CVSS vector, exploitability analysis, PoC, or workaround is provided. The root cause is missing skb consumption on an htc_tx_completion error path.
Mitigation direction
Apply vendor kernel updates that include the referenced stable ath11k fixes.
Prioritize systems using ath11k wireless hardware in availability-sensitive environments.
Check distribution advisories for backported fixes before relying on version numbers alone.
If updates are unavailable, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux systems for affected kernel versions and ath11k driver usage.
Confirm whether deployed kernel packages include the referenced stable commits or equivalent backports.
Review vendor advisories for affected product mapping and fixed package versions.
Monitor affected systems for memory pressure during ath11k wireless operation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50186 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.