btrfs: don't stash io_uring encoded data across -EAGAIN
- 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 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: don't stash io_uring encoded data across -EAGAIN Returning -EAGAIN while leaving btrfs_uring_encoded_data in the cmd PDU leaks if the request is cancelled or the ring exits before reissue. io_uring does not free driver PDU allocations on cleanup. Write: io_queue_sqe() always issues with IO_URING_F_NONBLOCK first, so return -EAGAIN before allocating and free data on every exit. Read: free on nowait -EAGAIN too; only -EIOCBQUEUED keeps the allocation for btrfs_uring_read_finished().
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 34310c442e175f286b4c06ab5caa4e0b267ea31c · fixed in 4d9c1e0a7fb2cfb1cc924acafc194d2c15c3e83e; From 34310c442e175f286b4c06ab5caa4e0b267ea31c · fixed in 51562a8cb11628d3a5e105b4c347ec5473e5745f
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 7.2.11