CVE-2026-98858: io_uring: fix task_work add use-after-free with SQPOLL

Published Oct 18, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iouring: fix taskwork add use-after-free with SQPOLL

For SQPOLL, the sqpoll thread runs taskwork off its own list and doesn't need to be told about it, so it can pop and complete a request as soon as mpscqpush() has published it. If that was the last request holding the ring alive, ioringexitwork() then frees the ctx, stops the thread, and with it the tctx, while ioreqnormalworkadd() is still looking at both after the push:

BUG: KASAN: slab-use-after-free in ioreqnormalworkadd+0x439/0x510 Read of size 4 at addr ff11000000ca0000 by task repro/55 (...) BUG: KASAN: slab-use-after-free in queueworkon+0x25/0x70 Write of size 8 at addr ff11000000c3bd00 by task repro/55

Hold an RCU read lock across the add, like ioreqlocalworkadd() already does, and have ioringexitwork() wait for a grace period for SQPOLL rings as well before freeing the ctx.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    For SQPOLL io_uring rings, hold an RCU read lock across task-work addition, and have io_ring_exit_work() wait for an RCU grace period before freeing the context.

Event History

Oct 18, 2026
CVE Published
via MITRE·03:51 PM
Data Sourced
via MITRE·03:51 PM
Description
Data Sourced
via NVD·04:17 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Linux kernel systems using io_uring rings configured with SQPOLL are exposed to the affected race. The issue specifically involves the SQPOLL thread processing task_work while a ring is being torn down.

2

What conditions are needed to trigger the use-after-free?

A request must be published to the SQPOLL task_work queue while teardown can free the io_uring context. The race is most relevant when that request is the last one keeping the ring alive, allowing io_ring_exit_work() to stop the SQPOLL thread and free associated state during task_work submission.

3

How is the issue fixed?

The fix holds an RCU read lock across task_work addition and makes io_ring_exit_work() wait for an RCU grace period before freeing the context for SQPOLL rings. The referenced stable kernel commits contain the available fixes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203