Security Resilience

CVE-2024-53136

Race Condition in Linux Kernel 4.19.323 – 4.19.325

Published
04 December 2024
Modified
04 August 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0042 35th percentile
Risk Priority 57 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-53136 is a high-severity Race Condition (CWE-362) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 35th 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 SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: mm: revert "mm: shmem: fix data-race in shmem_getattr()" Revert d949d1d14fa2 ("mm: shmem: fix data-race in shmem_getattr()") as suggested by Chuck [1]. It is causing deadlocks when accessing tmpfs over NFS.…

more

As Hugh commented, "added just to silence a syzbot sanitizer splat: added where there has never been any practical problem".

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-52740Same product: Linux Linux Kernel
CVE-2024-53121Same product: Linux Linux Kernel
CVE-2026-23411Same product: Linux Linux Kernel
CVE-2024-49859Same product: Linux Linux Kernel
CVE-2024-38613Same product: Linux Linux Kernel
CVE-2024-40953Same product: Linux Linux Kernel
CVE-2025-39726Same product: Linux Linux Kernel
CVE-2025-71078Same product: Linux Linux Kernel
CVE-2026-23161Same product: Linux Linux Kernel
CVE-2025-21943Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
4.19.323 — 4.19.325 · 5.4.285 — 5.5 · 5.10.229 — 5.11

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

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 race conditions, but does not prevent them at design or coding time.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

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-362, a class-level weakness, and none of its children carries one either.

References