Cyber Resilience

CVE-2023-32253

Published
02 August 2025
Modified
30 June 2026
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0030 22th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-32253 is a medium-severity Improper Resource Locking (CWE-413) vulnerability. Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

A flaw was found in the Linux kernel's ksmbd component. A deadlock is triggered by sending multiple concurrent session setup requests, possibly leading to a denial of service.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-44608Shared CWE-413
CVE-2025-3450Shared CWE-413
CVE-2023-28649Shared CWE-413
CVE-2023-2269Shared CWE-413
CVE-2023-2430Shared CWE-413
CVE-2025-69198Shared CWE-413
CVE-2023-33951Shared CWE-413
CVE-2026-32748Shared CWE-413

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, static analysis, coding standards) directly prevent improper locking defects from being introduced.

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.

finds

Security testing can detect locking defects but does not itself implement locking controls.

prevents

Secure development lifecycle requires proper resource management patterns that prevent improper locking.

prevents

Application security requirements can mandate exclusive-access controls and locking mechanisms.

prevents

Secure system architecture principles include concurrency and resource-locking design rules.

prevents

Secure coding standards directly prohibit missing or incorrect resource locks.

References