io_uring/tctx: work around xa_store() allocation error issue
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.1.120, Kernel 6.6.66, Kernel 6.12.5 and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.1 <6.1.120, >=6.2 <6.6.66, >=6.7 <6.12.5, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <42882b583095dcf747da6e3af1daeff40e27033e, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <7eb75ce7527129d7f1fee6951566af409a37a1c4, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <94ad56f61b873ffeebcc620d451eacfbdf9d40f0, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <d5b2ddf1f90c7248eff9630b95895c8950f2f36d, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <e05c070b401f6365c503e2b59f091331965c4fb9, =5.1, >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <3a84fa784710990964c1e35df743851ab2863898 | 6.1.120, 6.6.66, 6.12.5, 42882b583095dcf747da6e3af1daeff40e27033e, 7eb75ce7527129d7f1fee6951566af409a37a1c4, 94ad56f61b873ffeebcc620d451eacfbdf9d40f0, d5b2ddf1f90c7248eff9630b95895c8950f2f36d, e05c070b401f6365c503e2b59f091331965c4fb9, 3a84fa784710990964c1e35df743851ab2863898 |
| linux-kernel: Kernel | >=5.1.0 <5.10.253, >=5.11.0 <5.15.203, >=5.16.0 <6.1.120, >=6.2.0 <6.6.66, >=6.7.0 <6.12.5 | 5.10.253, 5.15.203, 6.1.120, 6.6.66, 6.12.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket