Vulnerability 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().
References
- https://git.kernel.org/stable/c/2797eb38773a96914ccedeec71eb2144645400b2
- https://git.kernel.org/stable/c/ada1fc725a4db407294ae90a0d40ef1c46f457f2
- https://git.kernel.org/stable/c/b6e8add5d79d1f6f819a054c833bab452bd7365d
FAQ
What is CVE-2026-98961?
CVE-2026-98961 is a documented vulnerability. 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_r...
How severe is CVE-2026-98961?
CVSS scoring is not yet available for CVE-2026-98961. Check NVD for updates.
Is there a patch for CVE-2026-98961?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.