CVE-2023-54041
published 2025-12-24CVE-2023-54041: In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided buffers…
PriorityP417low5.5
EPSS
0.17%
6.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 < ac48787f58d1068f4e06d627c1135784d64b4c72 | ac48787f58d1068f4e06d627c1135784d64b4c72 |
| linux | linux | >= cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 < c117c15927772d1624c29c092b6bd3f47c7faa48 | c117c15927772d1624c29c092b6bd3f47c7faa48 |
| linux | linux | >= cc3cec8367cba76a8ae4c271eba8450f3efc1ba3 < b4a72c0589fdea6259720375426179888969d6a2 | b4a72c0589fdea6259720375426179888969d6a2 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 5.18.0 < 6.1.24 | 6.1.24 |
| linux | linux_kernel | >= 6.2.0 < 6.2.11 | 6.2.11 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-g296-6qj4-g8f8: In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided
ghsa_unreviewed·2025-12-24
CVE-2023-54041 GHSA-g296-6qj4-g8f8: In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
OSV
CVE-2023-54041: In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided bu
osv·2025-12-24
CVE-2023-54041 CVE-2023-54041: In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided bu
In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided buffers, io_buffer structs are not being disposed of, leading to a memory leak. They can't be freed individually, because they are allocated in page-sized groups. They need to be added to some free list instead, such as io_buffers_cache. All callers already hold the lock protecting it, apart from when destroying buffers, so had to extend the lock there.
OSV
io_uring: fix memory leak when removing provided buffers
osv·2025-12-24
CVE-2023-54041 io_uring: fix memory leak when removing provided buffers
io_uring: fix memory leak when removing provided buffers
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
Red Hat
kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
vendor_redhat·2025-12-24·CVSS 5.5
CVE-2023-54041 [LOW] CWE-772 kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
A flaw was found in the Linux kernel's io_uring subsystem. When removing provided buffers, the system fails to properly dispose of `io_buffer` structures, leading to a memory leak. A local attacker could exploit this v
Debian
CVE-2023-54041: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring: f...
vendor_debian·2023
CVE-2023-54041 CVE-2023-54041: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring: f...
In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided buffers, io_buffer structs are not being disposed of, leading to a memory leak. They can't be freed individually, because they are allocated in page-sized groups. They need to be added to some free list instead, such as io_buffers_cache. All callers already hold the lock protecting it, apart from when destroying buffers, so had to extend the lock there.
Scope: local
bookworm: resolved (fixed in 6.1.25-1)
bullseye: resolved
forky: resolved (fixed in 6.1.25-1)
sid: resolved (fixed in 6.1.25-1)
trixie: resolved (fixed in 6.1.25-1)
No detection rules found.
No public exploits indexed.
Wiz
CVE-2023-54041 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54041 CVE-2023-54041 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54041 :
Linux Kernel vulnerability analysis and mitigation
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
Source : NVD
Published December 24, 2025
CNA Score N/A
Affected Technologies
Linux Kernel
Linux Debian
Has Public Exploit No
Has CISA KEV Exploit No
CISA KEV Release Date N/A
CISA KEV Due Date N/A
Exploitation
Bugzilla
CVE-2023-54041 kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
bugzilla·2025-12-24
CVE-2023-54041 [LOW] CVE-2023-54041 kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
CVE-2023-54041 kernel: Linux kernel: Memory leak in io_uring can lead to denial of service
In the Linux kernel, the following vulnerability has been resolved:
io_uring: fix memory leak when removing provided buffers
When removing provided buffers, io_buffer structs are not being disposed
of, leading to a memory leak. They can't be freed individually, because
they are allocated in page-sized groups. They need to be added to some
free list instead, such as io_buffers_cache. All callers already hold
the lock protecting it, apart from when destroying buffers, so had to
extend the lock there.
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025122440-CVE-2023-54041-57f4@gregkh/T
2025-12-24
Published