VYPR
Unrated severityNVD Advisory· Published Dec 30, 2025· Updated Apr 15, 2026

CVE-2022-50829

CVE-2022-50829

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A use-after-free bug in the Linux kernel's ath9k WiFi driver USB callback can lead to memory corruption or code execution.

Vulnerability

Overview

CVE-2022-50829 is a use-after-free vulnerability in the Linux kernel's ath9k WiFi driver, specifically in the ath9k_hif_usb_reg_in_cb() callback function for USB devices. The root cause is that a socket buffer (skb) can be freed inside ath9k_htc_rx_msg(), and then if usb_submit_urb() fails, the code attempts to free the same skb again, leading to a use-after-free condition. Additionally, if alloc_skb() fails, urb->context becomes NULL but rx_buf is not freed, causing a memory leak [1][2].

Exploitation

An attacker with physical access or the ability to inject malicious USB traffic into the system could trigger this bug by sending crafted USB packets to a device using the ath9k using the ath9k_htc` driver. The vulnerability is reachable from the USB completion handler, which is a common attack surface for the driver's receive path. No special privileges are required beyond the ability to interact with the USB device [3].

Impact

Successful exploitation could allow an attacker to corrupt kernel memory, potentially leading to a denial of service (system crash) or, in more severe cases, arbitrary code execution in the kernel context. The use-after-free can be leveraged to overwrite kernel objects and escalate privileges [4].

Mitigation

The fix was applied to the Linux kernel stable branches. Users should update to a kernel version containing the commit that removes the unnecessary nskb and clarifies skb ownership in the callback. No workaround is available; patching is required [1][1][2][3][4].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

9

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

9

News mentions

0

No linked articles in our index yet.