VulnerabilityPublished 28 Oct 2026

CVE-2026-99130: Linux kernel · io_uring/cancel: don't spin on local work the task can't run

Source GCVE Database

Authoritative record:CVE-2026-99130

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

Data as of 28 Oct 2026, 14:13 UTC

Severity

High

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

Patch: Available – fixed in fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7, 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa, 94d13387b96e50a4288f7bbdfe401189246a11a1

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-74p5-p638-5cc7

What to do

Upgrade Linux kernel to fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7, 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa or 94d13387b96e50a4288f7bbdfe401189246a11a1.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7	Fixed in fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7
LinuxLinux	Affected ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa	Fixed in 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa
LinuxLinux	Affected ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 94d13387b96e50a4288f7bbdfe401189246a11a1	Fixed in 94d13387b96e50a4288f7bbdfe401189246a11a1
LinuxLinux	Affected =6.4	Fixed in–

AI-suggested

A fix has been implemented that changes the behavior to allow the exiting task to sleep if it cannot run the local work, preventing indefinite spinning. The WARN_ON_ONCE() has been removed to reflect that handing a disabled ring to another thread is supported. Users should apply the official kernel update containing this fix once available.

Description

CVE-2026-99130 is a Linux kernel vulnerability in the io_uring subsystem where an exiting task can spin indefinitely on local work it cannot run. This occurs when a disabled io_uring ring is enabled by another task, causing the exiting task to burn CPU cycles or potentially panic the kernel if configured. The issue arises because the exiting task assumes it is the submitter of the ring and refuses to sleep while local work is pending, but this assumption is invalid for disabled rings enabled by other tasks.

References

Community reviews

Loading reviews…