Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53641

wifi: ath9k: hif_usb: fix memory leak of remain_skbs

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53641, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 6719e3797ec52cd144c8a5ba8aaab36674800585
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < d9899318660791141ea6002fda5577b2c5d7386e
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 320d760a35273aa815d58b57e4fd9ba5279a3489
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 59073060fe0950c6ecbe12bdc06469dcac62128d
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 9b9356a3014123f0ce4b50d9278c1265173150ab
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < f0931fc8f4b6847c72e170d2326861c0a081d680
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 8f02d538878c9b1501f624595eb22ee4e5e0ff84
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 7654cc03eb699297130b693ec34e25f77b17c947
  • Linux · Linux

    • affected 2.6.35
    • unaffected < 2.6.35
    • unaffected 4.19.283 – ≤ 4.19.*
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53641 badge
[![CVE-2023-53641](https://cveledger.app/badge/CVE-2023-53641.svg)](https://cveledger.app/cve/CVE-2023-53641)

Record last updated .