CVE-2024-53187Microsoft CVSS 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Microsoft advisory for CVE-2024-53187

Published
September 3, 2025
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2024-53187 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-53187. This page also shows what EchelonGraph holds for CVE-2024-53187, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products22

  • azl3 kernel 6.6.104.2-4 on Azure Linux 3.0
  • azl3 kernel 6.6.112.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.117.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-3 on Azure Linux 3.0
  • azl3 kernel 6.6.121.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.126.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.130.1-3 on Azure Linux 3.0
  • azl3 kernel 6.6.134.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.137.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.138.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.139.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.141.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.143.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.144.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.145.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-2 on Azure Linux 3.0
  • cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.202.1-1 on CBL Mariner 2.0

🧭 EchelonGraph on CVE-2024-53187

EchelonGraph score
5.5 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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> __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.

Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-53187, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (1)