Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2023-53641

medium

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of remain_skbs hif_dev->remain_skb is allocated and…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of remain_skbs hif_dev->remain_skb is allocated and used exclusively in ath9k_hif_usb_rx_stream(). It is implied that an allocated remain_skb is processed and subsequently freed (in error paths) only during the next call of ath9k_hif_usb_rx_stream(). So, if the urbs are deallocated between those two calls due to the device deinitialization or suspend, it is possible that ath9k_hif_usb_rx_stream() is not called next time and the allocated remain_skb is leaked. Our local Syzkaller instance was able to trigger that. remain_skb makes sense when receiving two consecutive urbs which are logically linked together, i.e. a specific data field from the first skb indicates a cached skb to be allocated, memcpy'd with some data and subsequently processed in the next call to ath9k_hif_usb_rx_stream(). Urbs deallocation supposedly makes that link irrelevant so we need to free the cached skb in those cases. Fix the leak by introducing a function to explicitly free remain_skb (if it is not NULL) when the rx urbs have been deallocated. remain_skb is NULL when it has not been allocated at all (hif_dev struct is kzalloced) or when it has been processed in next call to ath9k_hif_usb_rx_stream(). Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-10-07 16:15
Modified: 2026-11-05 21:17
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-05 21:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥2.6.35 <4.19.283, ≥4.20 <5.4.243, ≥5.5 <5.10.180, ≥5.11 <5.15.111, ≥5.16 <6.1.28, ≥6.2 <6.2.15

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/320d760a35273aa815d58b57e4fd9ba5279a3489
Patch / mitigation: https://git.kernel.org/stable/c/59073060fe0950c6ecbe12bdc06469dcac62128d
Patch / mitigation: https://git.kernel.org/stable/c/6719e3797ec52cd144c8a5ba8aaab36674800585
Patch / mitigation: https://git.kernel.org/stable/c/7654cc03eb699297130b693ec34e25f77b17c947
Patch / mitigation: https://git.kernel.org/stable/c/8f02d538878c9b1501f624595eb22ee4e5e0ff84
Patch / mitigation: https://git.kernel.org/stable/c/9b9356a3014123f0ce4b50d9278c1265173150ab
Patch / mitigation: https://git.kernel.org/stable/c/d9899318660791141ea6002fda5577b2c5d7386e
Patch / mitigation: https://git.kernel.org/stable/c/f0931fc8f4b6847c72e170d2326861c0a081d680

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 21:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs