CVE-2023-53802
Description
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function
It is stated that ath9k_htc_rx_msg() either frees the provided skb or passes its management to another callback function. However, the skb is not freed in case there is no another callback function, and Syzkaller was able to cause a memory leak. Also minor comment fix.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in ath9k_htc_rx_msg() of the Linux kernel occurs when an skb is not freed if no callback function is available, exploitable locally via Syzkaller.
Vulnerability
Description
In the Linux kernel's ath9k_htc wireless driver, the function ath9k_htc_rx_msg() is responsible for handling received frames (skbs). According to the commit message, the function is documented to either free the provided skb or pass its management to another callback function. However, when no callback function is present, the skb is not freed, leading to a memory leak. This issue was discovered by the Linux Verification Center (linuxtesting.org) using Syzkaller [1][2][3].
Attack
Vector and Prerequisites
An attacker would need local access to the system and the ability to send crafted wireless frames to an interface managed by the ath9k_htc driver. The vulnerability is triggered when ath9k_htc_rx_msg() is called and no callback function is registered, causing the skb to be leaked. Syzkaller demonstrated that the leak can be reliably reproduced, indicating that an unprivileged local user could cause repeated memory exhaustion [1][2][3].
Impact
Successful exploitation results in a gradual memory leak, potentially leading to denial of service (DoS) as system memory becomes depleted. The kernel may become unstable or crash due to out-of-memory conditions. There is no indication of code execution or privilege escalation from this vulnerability.
Mitigation
Stable kernel updates containing the fix are available. The commit requires adding an explicit kfree_skb() call for the case where no callback exists. Users should apply the patch from the stable kernel tree to prevent the leak [1][2][3].
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
2Patches
8b11f95f65cc568171c006c86564bc2222bf5ec246dfe006bc0c0614f143b5a84e51f7258bbfababb4f899b25e3985477Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/564bc2222bf50eb6cdee715a5431bf4dc9f923c1nvd
- git.kernel.org/stable/c/5a84e51f72580fc70066b03f3dac38421e702a0bnvd
- git.kernel.org/stable/c/68171c006c8645a3e0293a6c3e6037c6538ac1c5nvd
- git.kernel.org/stable/c/9b25e3985477ac3f02eca5fc1e0cc6850a3f7e69nvd
- git.kernel.org/stable/c/b11f95f65cc52ee3a756e6f6a88df37a203e25bdnvd
- git.kernel.org/stable/c/bbfababb4f899fe1556eac195f9774b6fe675fb6nvd
- git.kernel.org/stable/c/c0c0614f143b568cd0e9525d53cf12e5dcd11987nvd
- git.kernel.org/stable/c/ec246dfe006b2a8f36353f7489e4f525114db9a5nvd
News mentions
0No linked articles in our index yet.