btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 162d053e15fe985f754ef495a96eb3db970c43ed, Kernel 1baf3370e2dc5e6bd1368348736189457dab2a27, Kernel 50f993da945074b2a069da099a0331b23a0c89a0 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range If we get -ENOMEM while dropping file extent items in a given range, at btrfs_drop_extents(), due to failure to allocate memory when attempting to increment the reference count for an extent or drop the reference count, we handle it with a BUG_ON(). This is excessive, instead we can simply abort the transaction and return the error to the caller. In fact most callers of btrfs_drop_extents(), directly or indirectly, already abort the transaction if btrfs_drop_extents() returns any error. Also, we already have error paths at btrfs_drop_extents() that may return -ENOMEM and in those cases we abort the transaction, like for example anything that changes the b+tree may return -ENOMEM due to a failure to allocate a new extent buffer when COWing an existing extent buffer, such as a call to btrfs_duplicate_item() for example. So replace the BUG_ON() calls with proper logic to abort the transaction and return the error.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.29, >=39279cc3d2704cfbf9c35dcb5bdd392159ae4625 <162d053e15fe985f754ef495a96eb3db970c43ed, >=39279cc3d2704cfbf9c35dcb5bdd392159ae4625 <1baf3370e2dc5e6bd1368348736189457dab2a27, >=39279cc3d2704cfbf9c35dcb5bdd392159ae4625 <50f993da945074b2a069da099a0331b23a0c89a0, >=39279cc3d2704cfbf9c35dcb5bdd392159ae4625 <7fbcb635c8fc927d139f3302babcf1b42c09265c | 162d053e15fe985f754ef495a96eb3db970c43ed, 1baf3370e2dc5e6bd1368348736189457dab2a27, 50f993da945074b2a069da099a0331b23a0c89a0, 7fbcb635c8fc927d139f3302babcf1b42c09265c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket