Bug 2559629 (CVE-2026-98961) - CVE-2026-98961 kernel: btrfs: unlock inode and extent in caller when io_uring read extent fails
Summary: CVE-2026-98961 kernel: btrfs: unlock inode and extent in caller when io_uring...
Keywords:
Status: NEW
Alias: CVE-2026-98961
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-23 12:45 UTC by OSIDB Bzimport
Modified: 2026-10-27 17:51 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-23 12:45:21 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.