io_uring/rw: free potentially allocated iovec on cache put failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.1146.18.106.19In the Linux kernel, the following vulnerability has been resolved:
io_uring/rw: free potentially allocated iovec on cache put failure
If a read/write request goes through io_req_rw_cleanup() and has an allocated iovec attached and fails to put to the rw_cache, then it may end up with an unaccounted iovec pointer. Have io_rw_recycle() return whether it recycled the request or not, and use that to gauge whether to free a potential iovec or not.
From the CVE record · Linux
A Linux kernel read/write request can leave an allocated iovec pointer unaccounted for if cleanup fails to put the request in the rw_cache. The input does not specify an attacker action, access requirements, or whether user interaction is needed.
Operators running the Linux kernel should check their version against the vendor advisory; affected versions are not specified.