Description
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: commit partial buffers on retry Ring provided buffers are potentially only valid within the single execution context in which they were acquired. io_uring deals with this and invalidates them on retry. But on the networking side, if MSG_WAITALL is set, or if the socket is of the streaming type and too little was processed, then it will hang on to the buffer rather than recycle or commit it. This is problematic for two reasons: 1) If someone unregisters the provided buffer ring before a later retry, then the req->buf_list will no longer be valid. 2) If multiple sockers are using the same buffer group, then multiple receives can consume the same memory. This can cause data corruption in the application, as either receive could land in the same userspace buffer. Fix this by disallowing partial retries from pinning a provided buffer across multiple executions, if ring provided buffers are used.
Product status
c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 (git) before 3b53dc1c641f2884d4750fc25aaf6c36b90db606
c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 (git) before fe9da1812f8697a38f7e30991d568ec199e16059
c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 (git) before 21a4ddb0f5e933f372808c10b9ac704505751bb1
c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 (git) before 2eb7937b5fc7fcd90eab7bebb0181214b61b9283
c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 (git) before 41b70df5b38bc80967d2e0ed55cc3c3896bba781
6.4
Any version before 6.4
6.6.103 (semver)
6.12.44 (semver)
6.15.11 (semver)
6.16.2 (semver)
6.17 (original_commit_for_fix)
References
git.kernel.org/...c/3b53dc1c641f2884d4750fc25aaf6c36b90db606
git.kernel.org/...c/fe9da1812f8697a38f7e30991d568ec199e16059
git.kernel.org/...c/21a4ddb0f5e933f372808c10b9ac704505751bb1
git.kernel.org/...c/2eb7937b5fc7fcd90eab7bebb0181214b61b9283
git.kernel.org/...c/41b70df5b38bc80967d2e0ed55cc3c3896bba781
