CVE-2026-98961
- Source
- https://cve.org/CVERecord?id=CVE-2026-98961
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-98961.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-98961
- Downstream
- Published
- 2026-10-23T12:19:29Z
- Modified
- 2026-10-25T02:47:32Z
- Summary
- btrfs: unlock inode and extent in caller when io_uring read extent fails
- Details
-
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().
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98961.json" }- References
-
- https://git.kernel.org/stable/c/2797eb38773a96914ccedeec71eb2144645400b2
- https://git.kernel.org/stable/c/ada1fc725a4db407294ae90a0d40ef1c46f457f2
- https://git.kernel.org/stable/c/b6e8add5d79d1f6f819a054c833bab452bd7365d
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98961.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-98961
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git