CVE-2022-50829: wifi: ath9k: hif_usb: Fix use-after-free in ath9k_hif_usb_reg_in_cb()
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath9k: hif_usb: Fix use-after-free in ath9k_hif_usb_reg_in_cb()
It is possible that skb is freed in ath9k_htc_rx_msg(), then
usb_submit_urb() fails and we try to free skb again. It causes
use-after-free bug. Moreover, if alloc_skb() fails, urb->context becomes
NULL but rx_buf is not freed and there can be a memory leak.
The patch removes unnecessary nskb and makes skb processing more clear: it
is supposed that ath9k_htc_rx_msg() either frees old skb or passes its
managing to another callback function.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50829 is a Linux kernel bug in the ath9k USB Wi-Fi driver path. A memory object can be freed twice after an error, creating a use-after-free condition. Public sources do not provide CVSS, active exploitation evidence, or business-impact details.
Executive priority
Treat as a targeted kernel maintenance issue, not an emergency based on current evidence. Prioritize normal patch cycles, with faster action for Linux endpoints or appliances using ath9k USB Wi-Fi support.
Technical view
The issue is in ath9k_hif_usb_reg_in_cb(). ath9k_htc_rx_msg() may free an skb, then usb_submit_urb() failure leads to another free. The fix clarifies skb ownership and also addresses a related leak when alloc_skb() fails. It was found by Linux Verification Center using Syzkaller.
Likely exposure
Exposure is most relevant to Linux systems using the ath9k hif_usb USB Wi-Fi driver or kernels carrying that code. The CVE record references Linux kernel affected entries and multiple stable commits. Distribution-specific exposure depends on backports and kernel configuration.
Exploitation context
The source bundle states this was found by Syzkaller. It is not listed as KEV, and no cited source states active exploitation. Public information does not establish whether exploitation requires local access, specific USB Wi-Fi hardware, or other preconditions.
Researcher notes
The record lacks CVSS, CWE mapping, and exploitability analysis. The strongest evidence is the upstream stable patch description. Validate branch-specific status through kernel commits and distribution backport notes rather than relying only on version numbers.
Mitigation direction
Update affected Linux kernels using vendor or distribution security guidance.
Confirm the deployed kernel includes the referenced stable fix commit for its branch.
Prioritize systems with ath9k USB Wi-Fi hardware or the ath9k_hif_usb module enabled.
Validation and detection
Inventory Linux kernel versions and installed wireless drivers.
Check whether ath9k_hif_usb is present, loaded, or packaged.
Compare your kernel package against distribution advisories and referenced stable commits.
Document systems awaiting vendor-confirmed fixed kernels.
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-50829 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
10Source 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.
Dec 30, 2025, 12:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.