btrfs: clean up our handling of refs == 0 in snapshot delete
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2c47e605a91dde6b0514f689645e7ab336c8592a · < 7d1df13bf078ffebfedd361d714ff6cee1ff01b9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: clean up our handling of refs == 0 in snapshot delete
In reada we BUG_ON(refs == 0), which could be unkind since we aren't holding a lock on the extent leaf and thus could get a transient incorrect answer. In walk_down_proc we also BUG_ON(refs == 0), which could happen if we have extent tree corruption. Change that to return -EUCLEAN. In do_walk_down() we catch this case and handle it correctly, however we return -EIO, which -EUCLEAN is a more appropriate error code. Finally in walk_up_proc we have the same BUG_ON(refs == 0), so convert that to proper error handling. Also adjust the error message so we can actually do something with the information.
From the CVE record · Linux
The Linux kernel’s btrfs snapshot-deletion code can hit a BUG_ON when an extent reference count appears to be zero, either transiently or because of extent-tree corruption. This can cause a kernel crash; the input does not establish an attack path, required privileges, or user interaction.
Engineers running Linux kernels with btrfs should check their vendor’s advisory for affected versions, which are not specified here.