btrfs: fix the possible bioc_list memory leak during error
- 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 the possible bioc_list memory leak during error There are two possible ways to leak bioc memory on btrfs_ordered_extent::bioc_list: • An error occurred for btrfs_insert_one_raid_extent() Then the function btrfs_insert_raid_extent() immediately return without freeing any bioc in the bioc_list. • An ordered extent hit an IO error In that case the ordered extent will have BTRFS_ORDERED_IOERR set, and skip the call on btrfs_insert_raid_extent() completely. Fix the problem by: • Introduce a new helper, btrfs_cleanup_ordered_bioc_list() Which will remove all bioc from the bioc_list, and release the bioc. • Call the above helper for btrfs_insert_raid_extent() So that the cleanup helper is always called no matter what. • Call the above helper for btrfs_finish_one_ordered() This is called just before the final release on the ordered extent. This was reported by Sashiko when reviewing another patch.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ab69bf6f8970c09d3735c25094e9471d54365282 · fixed in d043c43d2b4ebcd75ee7f907948ef2847306d6b2; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in 83f0c973cffb184d019390ffdb5d31de5c85bc61; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in 1b4d4e890c2c85d0f6365b5a08c48b4bbf85deb0; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in bb4da45766d16503821f167054db76b735d89e94; From 02c372e1f016e5113217597ab37b399c4e407477 · fixed in afbe73778338e6d1ac8c4486fbdf33f0cc1f2624; 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