btrfs: unlock inode and extent in caller when io_uring read extent fails
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 34310c442e175f286b4c06ab5caa4e0b267ea31c · fixed in 2797eb38773a96914ccedeec71eb2144645400b2; From 34310c442e175f286b4c06ab5caa4e0b267ea31c · fixed in ada1fc725a4db407294ae90a0d40ef1c46f457f2; From 34310c442e175f286b4c06ab5caa4e0b267ea31c · fixed in b6e8add5d79d1f6f819a054c833bab452bd7365d
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11