In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths Since the buffers are mapped from userspace, it is prudent to use READ_ONCE() to read the value into a local variable, and use that for any other actions taken. Having a stable read of the buffer length avoids worrying about it changing after checking, or being read multiple times. Similarly, the buffer may well change in between it being picked and being committed. Ensure the looping for incremental ring buffer commit stops if it hits a zero sized buffer, as no further progress can be made at that point.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/390a61d284e1ced088d43928dfcf6f86fffdd780 Patch
- https://git.kernel.org/stable/c/695673eb5711ee5eb1769481cf1503714716a7d1 Patch
- https://git.kernel.org/stable/c/98b6fa62c84f2e129161e976a5b9b3cb4ccd117b 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-19 21:10
Affected (CPE criteria) 4
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*
References 4
- https://git.kernel.org/stable/c/390a61d284e1ced088d43928dfcf6f86fffdd780 Patch
- https://git.kernel.org/stable/c/695673eb5711ee5eb1769481cf1503714716a7d1 Patch
- https://git.kernel.org/stable/c/91f262ea2a76a02d9e37dba6637cfe6feebb20a8
- https://git.kernel.org/stable/c/98b6fa62c84f2e129161e976a5b9b3cb4ccd117b Patch