Cyber Resilience

CVE-2024-0641

Linux Kernel ≤ 6.6

Published
17 January 2024
Modified
21 November 2024
Patch / advisory
View 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 6th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-0641 is a medium-severity Deadlock (CWE-833) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 6th 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-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A denial of service vulnerability was found in tipc_crypto_key_revoke in net/tipc/crypto.c in the Linux kernel’s TIPC subsystem. This flaw allows guests with local user privileges to trigger a deadlock and potentially crash the system.

CWE(s)
CWE-833CWE-667

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.
attack.mitre.org →
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.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-0639Same product: Linux Linux Kernel
CVE-2023-28328Same product: Linux Linux Kernel
CVE-2023-6915Same product: Linux Linux Kernel
CVE-2023-28327Same product: Linux Linux Kernel
CVE-2023-4010Same product: Linux Linux Kernel
CVE-2023-1095Same product: Linux Linux Kernel
CVE-2023-4459Same product: Linux Linux Kernel
CVE-2024-0841Same product: Linux Linux Kernel
CVE-2023-6176Same product: Linux Linux Kernel
CVE-2023-33203Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.6 · ≤ 6.6
redhat
enterprise linux
8.0, 9.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)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

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 directly include code reviews, static analysis, and concurrency standards that prevent improper locking.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper lock acquisition/release patterns.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.32 Change management partial match
prevents

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

References