In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://git.kernel.org/stable/c/146a185f6c05ee263db715f860620606303c4633 Patch
- https://git.kernel.org/stable/c/2a5febbef40ce968e295a7aeaa5d5cbd9e3e5ad4 Patch
- https://git.kernel.org/stable/c/7d0dc28dae836caf7645fef62a10befc624dd17b Patch
- https://git.kernel.org/stable/c/8802766324e1f5d414a81ac43365c20142e85603 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · linuxNVD modified 2026-10-15 22:18
Affected (CPE criteria) 3
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*
References 5
- https://git.kernel.org/stable/c/146a185f6c05ee263db715f860620606303c4633 Patch
- https://git.kernel.org/stable/c/2a5febbef40ce968e295a7aeaa5d5cbd9e3e5ad4 Patch
- https://git.kernel.org/stable/c/7d0dc28dae836caf7645fef62a10befc624dd17b Patch
- https://git.kernel.org/stable/c/8802766324e1f5d414a81ac43365c20142e85603 Patch
- https://u1f383.github.io/slides/talks/2025_Hexacon-Deja_Vu_in_Linux_io_uring_Breaking_Memory_Sharing_Again_After_Generations_of_Fixes.pdf