CVE-2026-99800Linux vulnerability
CVE-2026-99800 is a vulnerability in Linux, not yet scored.
Why this priority: Not scored yet, and no exploitation signal.
Published · Updated · NVD status: Received
What it is
The record does not classify the weakness yet; the description below says what the reporter found.
How it is reached
The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.
What an attacker gains
Its impact has not been scored yet.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade Linux to a fixed version for your release line (7.3.2, 7.4-rc1).
Description from NVD
In the Linux kernel, the following vulnerability has been resolved:
io_uring: free the task context after a grace period
A task other than the owner can free a request, io_ring_exit_work() running the local task_work of a DEFER_TASKRUN ring for example, or io_do_iopoll() reaping completions. io_put_task() then takes the else branch:
percpu_counter_sub(&tctx->inflight, 1); if (unlikely(atomic_read(&tctx->in_cancel))) wake_up(&tctx->wait); put_task_struct(tctx->task);
The first line is what lets the owner leave io_uring_cancel_generic(), and on exec it frees the tctx right after. Nothing holds that off for the remaining three lines, the task reference only covers a tctx freed along with the task_struct. It used to work out because io_uring_del_tctx_node() took the uring_lock that the freeing side holds across io_put_task(), until that moved to tctx_lock.
Free the tctx with kfree_rcu(), and enter an RCU read section in io_put_task() before the count is dropped.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Linux. Start from where it runs and what it is connected to.
Trust boundaries in play
Questions to answer about your own systems
- Where does Linux run in your systems, and at which version?
- Which of those instances are reachable by people you do not trust?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.