Linux kernel use-after-free in io_uring io-wq enqueue
- Exploited
- No known exploitation
- Fix
- Fixed in 6.18.61, 7.3.2
- Who is exposed
- Not reported
Summary
The Linux kernel's io_uring component can enqueue work through a freed or NULL io-wq queue when a task other than the one that submitted a polled request reaps it during task exit. The fix hands these enqueues to the owning task before the queue is accessed.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
io_uring: defer foreign io-wq enqueues to task_work
An IOPOLL ring without DEFER_TASKRUN can be reaped by a task other than the one that submitted the I/O. If a polled request is marked REQ_F_REISSUE, io_free_batch_list() calls io_queue_iowq() with the original tctx. Ordinary task exit can tear down tctx->io_wq after draining only the tracked requests. The live request pins the task, but not its io-wq, so the foreign task can race io_wq_put_and_exit() and enqueue through a freed or NULL queue.
Forward foreign userspace enqueues to the owning task before accessing tctx->io_wq. Use a dedicated task_work callback so reissues still go straight to io-wq, and fail them if task_work is running in cancellation mode. Preserve the existing PF_KTHREAD cancellation path. This also covers the other callers of io_queue_iowq() without changing the worker-owned enqueue path.
What to do
Upgrade to a fixed version: 6.18.61, 7.3.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99798 (io_uring: defer foreign io-wq enqueues to task_work), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99798 (entry last updated 2026-11-20):
Affected:
- Linux Linux: fixed in 6.18.61; fixed in 7.3.2
- Linux Linux: from 6.19, fixed in 7.3.2; fixed in 6.18.61
Fixed versions: 6.18.61, 7.3.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99798 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/0ac8f069a8bd7a507df59c505182065ae720e946
- https://git.kernel.org/stable/c/5f7e7afd5418c63473f6ac3a05219e9e6e8a59d9
- https://git.kernel.org/stable/c/3de16279b43dc285ed2222aba06cebdc82fdb28b
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99798
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99798"}.Affected versions
- Linux Linuxfixed in 6.18.61; fixed in 7.3.2
- Linux LinuxFrom 6.19 · fixed in 7.3.2; fixed in 6.18.61
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99798 |
| Record | NVD · CVE-2026-99798 |
| Other links 3 | |
| Link | git.kernel.org · stable/c/0ac8f069a8bd7a507df59c505182065ae720e946 |
| Link | git.kernel.org · stable/c/5f7e7afd5418c63473f6ac3a05219e9e6e8a59d9 |
| Link | git.kernel.org · stable/c/3de16279b43dc285ed2222aba06cebdc82fdb28b |
Questions about CVE-2026-99798
Is CVE-2026-99798 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99798?
Linux: before 6.18.61; before 7.3.2. Linux: from 6.19 before 7.3.2; before 6.18.61.
Source: cve.now feed data
How do I fix CVE-2026-99798?
Upgrade to a fixed version: 6.18.61, 7.3.2.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.