CVE-2024-53187

Source
https://cve.org/CVERecord?id=CVE-2024-53187
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-53187.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-53187
Downstream
Related
Published
2024-12-27T13:49:30.268Z
Modified
2026-03-11T07:49:35.416555Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
io_uring: check for overflows in io_pin_pages
Details

In the Linux kernel, the following vulnerability has been resolved:

iouring: check for overflows in iopin_pages

WARNING: CPU: 0 PID: 5834 at iouring/memmap.c:144 iopinpages+0x149/0x180 iouring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __iouaddrmap+0xfb/0x2d0 iouring/memmap.c:183 ioringsmap iouring/iouring.c:2611 [inline] ioallocatescqurings+0x1c0/0x650 iouring/iouring.c:3470 iouringcreate+0x5b5/0xc00 iouring/iouring.c:3692 iouringsetup iouring/iouring.c:3781 [inline] ... </TASK>

iopinpages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/53xxx/CVE-2024-53187.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
2b188cc1bb857a9d4701ae59aa7768b5124e262e
Fixed
29eac3eca72d4c2a71122050c37cd7d8f73ac4f3
Fixed
aaa90844afd499c9142d0199dfda74439314c013
Fixed
0c0a4eae26ac78379d0c1db053de168a8febc6c9

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-53187.json"