Look up another CVE · open CVE-2024-53187 in the interactive tracker
CVE-2024-53187
io_uring: check for overflows in io_pin_pages
Published 2024-12-27 (22 months ago) by the Linux kernel CNA. Subsystem io_uring. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2024-53187 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.3-1 | Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.12.3-1 | Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.12.3-1 | Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
io_uring/memmap.c
- What this is
- IO_URINGMAINTAINERS section matched on io_uring/ · io-uring@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_IO_URING /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this code. Every release with an answer below compiles the affected file into the kernels it ships. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sidy
- ?
- not established - no Makefile entry for the affected file
- y
- built into the kernel image on every flavour - only a patch removes it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switch
- CONFIG_IO_URING
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2024-12-27 (22 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.24%, higher than 13.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- io_uring
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.1 | 6.11.11 | 29eac3eca72d |
| 5.1 | 6.12.2 | aaa90844afd4 |
| 5.1 | 6.13 | 0c0a4eae26ac |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2024-53187, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.