# CVE-2026-98961: linux: In the Linux kernel, the following vulnerability has been resolved:  btrfs: unlock inode and extent in caller when io...

CVE-2026-98961 is fixed in linux on 1 platform by DEBIAN-CVE-2026-98961 (version 7.2.11-1), released October 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-98961
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 23, 2026

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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.2.11-1 | [DEBIAN-CVE-2026-98961](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98961.md) | Oct 24, 2026 |

---

Data as of 2026-11-10T13:56:55Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.