Cyber Resilience

CVE-2024-53187

Memory Safety in Linux Kernel ≤ 6.11.11

Memory Safety
Published
27 December 2024
Modified
01 October 2025
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.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-53187 is a medium-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

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

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK>…

more

__io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

CWE(s)
CWE-190

Related Threats

CVEs Like This One

CVE-2024-52557Same product: Linux Linux Kernel
CVE-2024-46726Same product: Linux Linux Kernel
CVE-2026-45990Same product: Linux Linux Kernel
CVE-2025-21964Same product: Linux Linux Kernel
CVE-2023-52933Same product: Linux Linux Kernel
CVE-2024-37356Same product: Linux Linux Kernel
CVE-2025-21962Same product: Linux Linux Kernel
CVE-2023-42752Same product: Linux Linux Kernel
CVE-2024-38661Same product: Linux Linux Kernel
CVE-2025-21711Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
≤ 6.11.11 · 6.12 — 6.12.2

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)
  • V5.2.6

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 require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

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
detects

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

A.8.26 Application security requirements partial match
degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

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

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References