Description
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.
Product status
ae98dbf43d755b4e111fcd086e53939bef3e9a1a (git) before 695673eb5711ee5eb1769481cf1503714716a7d1
ae98dbf43d755b4e111fcd086e53939bef3e9a1a (git) before 390a61d284e1ced088d43928dfcf6f86fffdd780
ae98dbf43d755b4e111fcd086e53939bef3e9a1a (git) before 98b6fa62c84f2e129161e976a5b9b3cb4ccd117b
6.12
Any version before 6.12
6.12.49 (semver)
6.16.5 (semver)
6.17 (original_commit_for_fix)
References
git.kernel.org/...c/695673eb5711ee5eb1769481cf1503714716a7d1
git.kernel.org/...c/390a61d284e1ced088d43928dfcf6f86fffdd780
git.kernel.org/...c/98b6fa62c84f2e129161e976a5b9b3cb4ccd117b
