CVE-2026-98961Published

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

Exact source revision recorded 23 Oct 2026 16:01:20 UTC. It does not establish the source's current position. Latest evidence.

Recorded JSON

cve-program · CVE-2026-98961

Published

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

Source published: 23 Oct 2026 12:19:29 UTC
Source modified: 23 Oct 2026 12:19:29 UTC
Observed here: 23 Oct 2026 16:01:20 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.