io_uring: preserve task restrictions across exec
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
io_uring: preserve task restrictions across exec
Per-task restrictions apply to all rings created by a task. Once installed, they should not be dropped across exec.
For a task that has used io_uring, the exec cancellation path calls __io_uring_free(). This frees both the task context and the per-task restriction, so a ring created after exec is unrestricted.
Split task context cleanup into io_uring_free_tctx(), and use it from the exec cancellation path. Keep __io_uring_free() for final task cleanup, where both the context and restriction are released.
From the CVE record · Linux
The Linux kernel can drop per-task io_uring restrictions during exec after a task has used io_uring. A local task in that condition can create a new, unrestricted ring after exec. No user interaction is described.
Engineers running Linux kernels that may be affected should check their kernel version against the vendor advisory; affected versions are not specified in the input.