io_uring/kbuf: check if target buffer list is still legacy on recycle
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c7fb19428d67dd0a2a78a4f237af01d39c78dc5a · < c2c185be5c85d37215397c8e8781abf0a69bec1f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
io_uring/kbuf: check if target buffer list is still legacy on recycle
There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
From the CVE record · Linux
A race in Linux kernel io_uring/kbuf can allow a buffer list to change from legacy to ring-provided between buffer selection and recycling. An attacker able to trigger a request forced through io-wq could cause legacy recycling to run without confirming that the list still exists and is the correct type. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with io_uring/kbuf should check their kernel against the vendor advisory; affected versions are not specified.