VulnerabilityPublished 23 Oct 2026

CVE-2026-98960: Linux kernel · btrfs: don't stash io_uring encoded data across -EAGAIN

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 51562a8cb11628d3a5e105b4c347ec5473e5745f or 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 51562a8cb11628d3a5e105b4c347ec5473e5745f, 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e

Exploitation evidence

Disclosed: evidence found.
CVE published 23 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.

What to do

Upgrade Linux kernel to 51562a8cb11628d3a5e105b4c347ec5473e5745f or 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 34310c442e175f286b4c06ab5caa4e0b267ea31c, < 51562a8cb11628d3a5e105b4c347ec5473e5745f	Fixed in 51562a8cb11628d3a5e105b4c347ec5473e5745f
LinuxLinux	Affected ≥ 34310c442e175f286b4c06ab5caa4e0b267ea31c, < 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e	Fixed in 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e
LinuxLinux	Affected =6.13	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: don't stash io_uring encoded data across -EAGAIN Returning -EAGAIN while leaving btrfs_uring_encoded_data in the cmd PDU leaks if the request is cancelled or the ring exits before reissue. io_uring does not free driver PDU allocations on cleanup. Write: io_queue_sqe() always issues with IO_URING_F_NONBLOCK first, so return -EAGAIN before allocating and free data on every exit. Read: free on nowait -EAGAIN too; only -EIOCBQUEUED keeps the allocation for btrfs_uring_read_finished().

References

Community reviews

Loading reviews…