LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53802: wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the ath9k_htc Wi-Fi driver path. If the receive message handler has no callback, a network buffer may not be freed. The public record does not provide CVSS, impact severity, or evidence of active exploitation.

Executive priority

Treat as routine kernel hygiene unless ath9k_htc Wi-Fi devices are common in the environment. No source indicates active exploitation or high-impact compromise, but memory leaks can affect availability over time.

Technical view

ath9k_htc_rx_msg() is expected to free the supplied skb or transfer ownership to a callback. When no callback exists, the skb was left allocated, and Syzkaller reproduced a memory leak. Kernel stable commits are referenced as the fix source.

Likely exposure

Exposure appears limited to Linux systems using the ath9k_htc Wi-Fi driver or affected kernel builds carrying that code. Server fleets without this wireless driver or hardware are less likely exposed.

Exploitation context

The source bundle reports Syzkaller discovery by Linux Verification Center. It does not cite public exploitation, KEV listing, exploit availability, privilege requirements, or a demonstrated security impact beyond memory leak.

Researcher notes

Key evidence is narrow: a missing skb free path in ath9k_htc_rx_msg(), found by Syzkaller and resolved through Linux stable commits. The record lacks CVSS, CWE, exploitability detail, and downstream distribution status.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems using ath9k_htc-supported wireless hardware.
  • Check Linux distribution advisories for packaged kernel status.
  • Retire or upgrade affected kernel branches where fixes are unavailable.

Validation and detection

  • Inventory kernels and loaded modules for ath9k_htc usage.
  • Compare installed kernel builds against vendor advisory fixed versions.
  • Confirm the relevant stable patch is included in downstream source packages.
  • Monitor systems for unusual kernel memory pressure on exposed wireless hosts.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2023-53802 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08unaffected
LinuxLinux2.6.35, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.