CVE-2026-53191

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <f40570fda3f3a1f96aeaa4aef665ba274b2810b5, 6.12, <=7.0.*, <=*, <=6.12.*, 6.12.94, 7.1, <=6.18.*, ae98dbf43d755b4e111fcd086e53939bef3e9a1a, 0, 7.0.13, <6.12, <4973232a67e4137ab9399f504f7f2bdd847f96d2, <ed46f39c47eb5530a9c161481a2080d3a869cfaf, 6.18.36, <0bbc9481f970b0b4ddb08cfa464db1cc93b74b56

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.

Gravité et risque d'exploitation

CVE-2026-53191 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <f40570fda3f3a1f96aeaa4aef665ba274b2810b5, 6.12, <=7.0.*, <=*, <=6.12.*, 6.12.94, 7.1, <=6.18.*, ae98dbf43d755b4e111fcd086e53939bef3e9a1a, 0, 7.0.13, <6.12, <4973232a67e4137ab9399f504f7f2bdd847f96d2, <ed46f39c47eb5530a9c161481a2080d3a869cfaf, 6.18.36, <0bbc9481f970b0b4ddb08cfa464db1cc93b74b56) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références