Cyber Resilience

CVE-2023-33951

Race Condition in Redhat Enterprise Linux 8.0 … 9.0

Published
24 July 2023
Modified
18 February 2026
Patch / advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
EPSS Score 0.0034 27th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-33951 is a medium-severity Improper Resource Locking (CWE-413) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A race condition vulnerability was found in the vmwgfx driver in the Linux kernel. The flaw exists within the handling of GEM objects. The issue results from improper locking when performing operations on an object. This flaw allows a local…

more

privileged user to disclose information in the context of the kernel.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-33952Same product: Linux Linux Kernel
CVE-2024-0641Same product: Linux Linux Kernel
CVE-2024-0639Same product: Linux Linux Kernel
CVE-2023-33203Same product: Linux Linux Kernel
CVE-2023-6531Same product: Linux Linux Kernel
CVE-2023-4732Same product: Linux Linux Kernel
CVE-2024-27005Same product: Linux Linux Kernel
CVE-2023-2430Same product: Linux Linux Kernel
CVE-2023-28328Same product: Linux Linux Kernel
CVE-2023-6915Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
≤ 6.3.9
redhat
enterprise linux
8.0, 9.0
redhat
enterprise linux for real time
8.0
redhat
enterprise linux for real time for nfv
8.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-362

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

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.

prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References