io_uring/tctx: work around xa_store() allocation error issue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2b188cc1bb857a9d4701ae59aa7768b5124e262e · < 7eb75ce7527129d7f1fee6951566af409a37a1c4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
io_uring/tctx: work around xa_store() allocation error issue
syzbot triggered the following WARN_ON:
WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51
which is the
WARN_ON_ONCE(!xa_empty(&tctx->xa));
sanity check in __io_uring_free() when a io_uring_task is going through its final put. The syzbot test case includes injecting memory allocation failures, and it very much looks like xa_store() can fail one of its memory allocations and end up with ->head being non-NULL even though no entries exist in the xarray.
Until this issue gets sorted out, work around it by attempting to iterate entries in our xarray, and WARN_ON_ONCE() if one is found.
From the CVE record · Linux
In the Linux kernel, an xa_store() allocation failure can leave an io_uring task's xarray appearing nonempty and trigger a warning when the task is freed. This was observed in a syzbot test that injected memory allocation failures; the input does not establish an attacker action or specify network, authentication, or user-interaction conditions.
Engineers running the Linux kernel should check affected versions in the vendor advisory; none are specified here.