CVE-2023-32247
Linux Kernel 5.15 – 5.15.145
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-32247 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 11% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability is a resource consumption flaw, tracked as CWE-401, in the Linux kernel's ksmbd component that implements an in-kernel SMB server. It occurs during handling of SMB2_SESSION_SETUP commands and allows uncontrolled allocation that can exhaust system resources, producing a denial-of-service condition. The affected software is the Linux kernel containing the ksmbd module; the issue carries a CVSS 3.1 score of 7.5.
An unauthenticated network attacker can send a series of specially crafted SMB2_SESSION_SETUP requests to trigger the flaw. Because the attack requires no credentials or user interaction and can be launched remotely, successful exploitation results in a high-impact availability loss on the target system while leaving confidentiality and integrity unaffected.
The EPSS score for this CVE started low after the July 2023 disclosure, rose materially to a peak of 0.0914 on 2025-01-22, and has since fallen to 0.0009, indicating a period of increased exploitation interest well after public release. Red Hat, NetApp, and Zero Day Initiative have published advisories referencing the issue for tracking and mitigation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-36504
Vulnerability Data
A flaw was found in the Linux kernel's ksmbd, a high-performance in-kernel SMB server. The specific flaw exists within the handling of SMB2_SESSION_SETUP commands. The issue results from the lack of control of resource consumption. An attacker can leverage this…
more
vulnerability to create a denial-of-service condition on the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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.
Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.
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.
Security testing in development can detect unreleased memory, providing partial coverage of the weakness.
Secure development life cycle mandates memory-management practices that reduce missing-release defects.
Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.
Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.
Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.
Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.