# CVE-2026-98960: btrfs: don't stash io_uring encoded data across -EAGAIN


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-98960, DEBIAN-CVE-2026-98960, GHSA-wr36-cvhp-r8q2, UBUNTU-CVE-2026-98960

## What is CVE-2026-98960?

CVE-2026-98960 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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().

## Which versions are affected by CVE-2026-98960?


## How do I fix CVE-2026-98960?

Upgrade to a fixed version.

## Is CVE-2026-98960 being exploited?

There is no known exploitation of CVE-2026-98960 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98960 and fix it if it is affected.

What it is: CVE-2026-98960 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98960 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98960/ (Markdown: https://insights.sbomify.com/CVE-2026-98960/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98960
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98960
- OSV: https://osv.dev/vulnerability/CVE-2026-98960

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98960/
Summaries are generated and may contain mistakes; the official description above is the record.