btrfs: remove BUG_ON()'s in add_new_free_space()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.456.4.106.5In the Linux kernel, the following vulnerability has been resolved:
btrfs: remove BUG_ON()'s in add_new_free_space()
At add_new_free_space() we have these BUG_ON()'s that are there to deal with any failure to add free space to the in memory free space cache. Such failures are mostly -ENOMEM that should be very rare. However there's no need to have these BUG_ON()'s, we can just return any error to the caller and all callers and their upper call chain are already dealing with errors.
So just make add_new_free_space() return any errors, while removing the BUG_ON()'s, and returning the total amount of added free space to an optional u64 pointer argument.
From the CVE record · Linux
The Linux kernel's btrfs add_new_free_space() function can hit a BUG_ON() when adding free space to its in-memory cache fails, most often because of a rare memory-allocation failure. This can crash the kernel; the input does not establish an attacker-controlled trigger or specify access or user-interaction requirements.
Engineers running Linux kernels with btrfs should check their kernel; affected versions are not specified.