Security Resilience

CVE-2024-0639

Redhat Enterprise Linux 8.0 … 9.0

Published
17 January 2024
Modified
21 July 2026
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.0018 7th 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-2024-0639 is a medium-severity Deadlock (CWE-833) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 7th 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 due to a deadlock was found in sctp_auto_asconf_init in net/sctp/socket.c in the Linux kernel’s SCTP subsystem. This flaw allows guests with local user privileges to trigger a deadlock and potentially crash the system.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
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.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-0641Same product: Linux Linux Kernel
CVE-2023-3812Same product: Linux Linux Kernel
CVE-2023-3640Same product: Linux Linux Kernel
CVE-2023-2019Same product: Linux Linux Kernel
CVE-2024-0646Same product: Linux Linux Kernel
CVE-2023-6176Same product: Linux Linux Kernel
CVE-2023-4459Same product: Linux Linux Kernel
CVE-2023-1095Same product: Linux Linux Kernel
CVE-2023-6915Same product: Linux Linux Kernel
CVE-2023-28327Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
≤ 6.4.16
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

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

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 partial match
blocks

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

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.

blocks

A.8.25 mandates a secure SDLC process with checkpoints, secure coding, testing and training; none of those steps stop an existing deadlock from being exploitable, they only aim to reduce the chance one is introduced

blocks

A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, fail securely, security by design, etc.) and performing design reviews; deadlock is a runtime concurrency flaw in implementation or threading logic that these principles and reviews do not stop from being introduced or exploited.

prevents

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

finds

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

blocks

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

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-667, a class-level weakness, and none of its children carries one either.

References