Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-53187io_uring: check for overflows in io_pin_pages

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.

Timeline

  1. ID reserved

    By Linux

  2. · 38 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-53187, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < f1938217aee05be1c1dc53f581a3c353d033b508
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 1a0aecabff72a95d240e6d7645949bfe0620dcd7
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < aaa90844afd499c9142d0199dfda74439314c013
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 0c0a4eae26ac78379d0c1db053de168a8febc6c9
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.11.11 – ≤ 6.11.*
    • unaffected 6.12.2 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-53187 badge
[![CVE-2024-53187](https://cveledger.app/badge/CVE-2024-53187.svg)](https://cveledger.app/cve/CVE-2024-53187)

Record last updated .