Answer in brief
CVE-2026-98858 records a Unknown severity vulnerability in io_uring: fix task_work add use-after-free with SQPOLL. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=af5d68f8892f8ee8f137648b79ceb2abc153a19b <42b3332efacfd2140be4cd0dedad4fb96b8ae90e || >=af5d68f8892f8ee8f137648b79ceb2abc153a19b <891bd8335a0de3bb15c3b797ce3026bbb0dbef6c || >=af5d68f8892f8ee8f137648b79ceb2abc153a19b <395b25968fe854d4efaa19a8e9b7a5b6d1b3eea3 || >=af5d68f8892f8ee8f137648b79ceb2abc153a19b <a92193c91e8839fe5fc209616ea95465ae4b919d | 42b3332efacfd2140be4cd0dedad4fb96b8ae90e, 891bd8335a0de3bb15c3b797ce3026bbb0dbef6c, 395b25968fe854d4efaa19a8e9b7a5b6d1b3eea3, a92193c91e8839fe5fc209616ea95465ae4b919d |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring: fix task_work add use-after-free with SQPOLL For SQPOLL, the sqpoll thread runs task_work off its own list and doesn't need to be told about it, so it can pop and complete a request as soon as mpscq_push() has published it. If that was the last request holding the ring alive, io_ring_exit_work() then frees the ctx, stops the thread, and with it the tctx, while io_req_normal_work_add() is still looking at both after the push: BUG: KASAN: slab-use-after-free in io_req_normal_work_add+0x439/0x510 Read of size 4 at addr ff11000000ca0000 by task repro/55 (...) BUG: KASAN: slab-use-after-free in queue_work_on+0x25/0x70 Write of size 8 at addr ff11000000c3bd00 by task repro/55 Hold an RCU read lock across the add, like io_req_local_work_add() already does, and have io_ring_exit_work() wait for a grace period for SQPOLL rings as well before freeing the ctx.
Quoted source text, attributed separately from HOL analysis.