# CVE-2026-98961: btrfs: unlock inode and extent in caller when io_uring read extent fails


- **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-98961, DEBIAN-CVE-2026-98961, GHSA-3xcr-f59c-pjvq, UBUNTU-CVE-2026-98961

## What is CVE-2026-98961?

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

### Official description

In the Linux kernel, the following vulnerability has been resolved:

btrfs: unlock inode and extent in caller when io_uring read extent fails

btrfs_uring_read_extent() runs only after btrfs_encoded_read() has taken
the inode shared lock and the extent lock.  On failure it used to unlock
in out_fail, and a pages-array allocation failure returned -ENOMEM
without unlocking at all.

Unlock in the caller instead on all failure returns, matching the
copy_to_user() error path.  The deferred -EIOCBQUEUED path still unlocks
in btrfs_uring_read_finished().

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


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

Upgrade to a fixed version.

## Is CVE-2026-98961 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98961 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98961 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-98961/ (Markdown: https://insights.sbomify.com/CVE-2026-98961/index.md)
```

## Sources

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

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