Security Resilience

CVE-2023-53199

Linux Kernel 2.6.38 – 4.19.276

Published
15 September 2025
Modified
03 December 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0016 5th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-53199 is a medium-severity Missing Release of Resource after Effective Lifetime (CWE-772) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: clean up skbs if ath9k_hif_usb_rx_stream() fails Syzkaller detected a memory leak of skbs in ath9k_hif_usb_rx_stream(). While processing skbs in ath9k_hif_usb_rx_stream(), the already allocated skbs in skb_pool are…

more

not freed if ath9k_hif_usb_rx_stream() fails. If we have an incorrect pkt_len or pkt_tag, the input skb is considered invalid and dropped. All the associated packets already in skb_pool should be dropped and freed. Added a comment describing this issue. The patch also makes remain_skb NULL after being processed so that it cannot be referenced after potential free. The initialization of hif_dev fields which are associated with remain_skb (rx_remain_len, rx_transfer_len and rx_pad_len) is moved after a new remain_skb is allocated. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-43054Same product: Linux Linux Kernel
CVE-2025-71232Same product: Linux Linux Kernel
CVE-2024-53074Same product: Linux Linux Kernel
CVE-2026-53251Same product: Linux Linux Kernel
CVE-2024-47733Same product: Linux Linux Kernel
CVE-2023-53152Same product: Linux Linux Kernel
CVE-2026-43314Same product: Linux Linux Kernel
CVE-2023-22996Same product: Linux Linux Kernel
CVE-2026-23219Same product: Linux Linux Kernel
CVE-2026-53154Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
2.6.38 — 4.19.276 · 4.20 — 5.4.235 · 5.5 — 5.10.173

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing resource releases through dynamic analysis or stress testing.

Requiring documented development standards and tools can mandate explicit resource-release patterns in code.

Resource-quota allocation limits the blast radius of an unreleased-resource exhaustion condition.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

DE.CM-09 partial match
blocks

Runtime monitoring may surface resource-exhaustion symptoms but does not address release logic.

ID.AM-08 partial match
blocks

Lifecycle management explicitly requires handling resources through end-of-life including release.

PR.IR-04 partial match
blocks

Capacity monitoring can detect exhaustion caused by unreleased resources but does not prevent the root defect.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent missing resource-release defects during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes
degrades

Explicit information-deletion requirements directly address timely release of resources after use.

References