btrfs: fix transaction use-after-free in raid stripe insertion
- 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.6.158, 6.12.111, 6.18.53, 7.2.7
- 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: fix transaction use-after-free in raid stripe insertion If allocation of a RAID stripe extent fails, btrfs_insert_one_raid_extent() aborts and ends the transaction before returning -ENOMEM. btrfs_finish_one_ordered(), the production caller through btrfs_insert_raid_extent(), still owns the transaction handle. It handles the error by aborting the transaction and then reaches the common exit path, which ends the transaction again. The premature end can free the handle and drop its transaction reference. Transaction cleanup can then free the transaction before the caller's second abort accesses the handle and transaction, resulting in use-after-free. Keep the abort at the failure site, but let the caller's common exit path end the transaction once, after it has finished using both objects.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ab69bf6f8970c09d3735c25094e9471d54365282 · fixed in 089d9c45ea49ffffe55a8fe08d0ce2536626e90a; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in b185bdf30313e213fa1c887fe22fc3d513c061d9; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in 2fbfd02bdfe12b20bd3cc7a3190fb32e3f7072f5; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in b7b94923b3b5774d85a2a7c8d6eb9e3e0ef66685; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in a8813a923f9e43f788b357fb55c35f7f6ed6f98c; From 6.6.130 · fixed in 6.6.158
- Linux Linux
6.7
- KernelLinux
fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; fixed in 6.18.53; From 6.13.0 · fixed in 7.2.7