Skip to main content
VulnerabilityPublished

CVE-2026-99798: Linux kernel · io_uring: defer foreign io-wq enqueues to task_work

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99798· High

Not known to be exploited · fixed in 7.3.2 : patch Linux kernel soon.

Data as of 20 Nov 2026, 11:04 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 7.3.2, 6.18.61, 5f7e7afd5418c63473f6ac3a05219e9e6e8a59d9 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <6.18.61
  • <7.3.2
Fixed in
  • 7.3.2
  • 6.18.61
  • 5f7e7afd5418c63473f6ac3a05219e9e6e8a59d9
  • 3de16279b43dc285ed2222aba06cebdc82fdb28b
  • 0ac8f069a8bd7a507df59c505182065ae720e946

AI-suggested

A fix has been implemented in the Linux kernel to defer foreign io-wq enqueues to the owning task via task_work callbacks. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to the patched kernel version is the recommended mitigation.

Description

A vulnerability in the Linux kernel's io_uring subsystem allows a race condition where a foreign task can enqueue I/O work to a freed or null I/O work queue. This occurs because an IOPOLL ring without DEFER_TASKRUN can be reaped by a different task than the one that submitted the I/O, leading to potential use-after-free scenarios. The issue has been addressed by deferring foreign userspace enqueues to the owning task using a dedicated task_work callback.

References

Community reviews

Loading reviews…