LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54275: wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup

In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup crypto_alloc_shash() allocates resources, which should be released by crypto_free_shash(). When ath11k_peer_find() fails, there has memory leak. Add missing crypto_free_shash() to fix this.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54275 is a Linux kernel memory leak in the ath11k Wi-Fi driver. If a peer lookup fails after a crypto object is allocated, the driver did not release that object. The source does not provide CVSS, impact scoring, or evidence of active exploitation.

Executive priority

Treat as a targeted kernel maintenance issue unless your environment relies heavily on ath11k wireless devices. Prioritize normal patch cycles, escalating where wireless Linux endpoints are exposed or stability is business-critical.

Technical view

The bug is in ath11k_peer_rx_frag_setup. crypto_alloc_shash() allocates resources that should be released with crypto_free_shash(). When ath11k_peer_find() fails, that release was missing. Kernel stable commits add the missing cleanup path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the ath11k Wi-Fi driver code in use. The bundle does not map fixes to Linux distributions, packages, hardware models, or runtime configuration requirements.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, or KEV listing. The issue is described as a memory leak fix, but the sources do not quantify denial-of-service feasibility or required attacker position.

Researcher notes

Evidence is limited to the CVE record and upstream stable commit references. There is no CVSS vector, CWE, exploit report, or distro-specific advisory in the bundle, so severity and practical exploitability remain unclear.

Mitigation direction

  • Check Linux distribution advisories for fixed kernel packages containing the stable commits.
  • Prioritize kernel updates on systems using the ath11k Wi-Fi driver.
  • Confirm whether affected fleet assets actually load or require ath11k.
  • If no vendor fix is available, follow vendor guidance rather than custom workarounds.

Validation and detection

  • Inventory Linux kernel versions across systems with wireless capability.
  • Identify systems where the ath11k driver is present or loaded.
  • Compare installed kernels against vendor advisories and referenced stable commits.
  • Track remediation through kernel package versions, not only upstream commit hashes.
Prepared
Confidence
medium
Sources
7

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-54275 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
6Source 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
LinuxLinux243874c64c8137bc90455200a7735da72836ecab, 243874c64c8137bc90455200a7735da72836ecab, 243874c64c8137bc90455200a7735da72836ecab, 243874c64c8137bc90455200a7735da72836ecab, 243874c64c8137bc90455200a7735da72836ecabunaffected
LinuxLinux5.7, 0, 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.