CVE-2024-53187
Linux kernel: integer overflow
- Risk score
- 52/100
- CVSS
- 5.5 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 27 Dec 2024
Open in the live forecast Today's forecast
What to know
- What it is
- 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: <TA…
- Affected
- Linux kernel
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Linux kernel: Amber, patch this week. In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: restore network header before routing and forwarding ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while skb_network_header() points at the IPv6 header. When segments_left > 0, ipv6_srh_rcv() previously restored the …
The flaws
- CVE-2024-53187: Integer overflow (CVSS 5.5 · EPSS 0%)
- CVE-2026-98096: Out-of-bounds write (CVSS 7.4 · EPSS 1%)
- CVE-2026-98115: Race condition (CVSS 8.8 · EPSS 0%)
- CVE-2026-98117: Use-after-free (CVSS 7.8 · EPSS 0%)
The fix
Fix: Apply the vendor's security update; see the linked advisory.
Who is exposed: Linux kernel
Where it stands
- No known exploitation
How it unfolded
- 3 Nov, Ubuntu security notices (official): USN-8962-1: Linux kernel (Azure CVM) vulnerabilities
- 3 Nov, Ubuntu security notices (official): USN-8965-1: Linux kernel (BlueField) vulnerabilities
- 3 Nov, Ubuntu security notices (official): USN-8963-1: Linux kernel (NVIDIA Tegra) vulnerabilities
- 3 Nov, Ubuntu security notices (official): USN-8961-1: Linux kernel vulnerabilities
Connects to
- Same weakness: Integer overflow (CWE-190). 158 other warnings in 30 days
- Same product: Earlier Linux kernel warnings. 105 in the last 90 days
Why it is Yellow
- CVSS 5.5 medium
- On your watchlist: linux kernel
- Named in a government or vendor bulletin
Government and vendor bulletins
References
- https://ubuntu.com/security/notices/USN-8961-1
- https://ubuntu.com/security/notices/USN-8963-1
- https://ubuntu.com/security/notices/USN-8965-1
- https://ubuntu.com/security/notices/USN-8962-1
- https://git.kernel.org/stable/c/0c0a4eae26ac78379d0c1db053de168a8febc6c9
- https://git.kernel.org/stable/c/1a0aecabff72a95d240e6d7645949bfe0620dcd7
- https://git.kernel.org/stable/c/29eac3eca72d4c2a71122050c37cd7d8f73ac4f3
- https://git.kernel.org/stable/c/aaa90844afd499c9142d0199dfda74439314c013
- https://git.kernel.org/stable/c/f1938217aee05be1c1dc53f581a3c353d033b508
Original description
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.
Last activity 3 Nov 2026. Patch Forecast updates every hour.