btrfs: fix transaction abort on set received ioctl due to item overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 · < 87f2c46003fce4d739138aab4af1942b1afdadac| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix transaction abort on set received ioctl due to item overflow
If the set received ioctl fails due to an item overflow when attempting to add the BTRFS_UUID_KEY_RECEIVED_SUBVOL we have to abort the transaction since we did some metadata updates before.
This means that if a user calls this ioctl with the same received UUID field for a lot of subvolumes, we will hit the overflow, trigger the transaction abort and turn the filesystem into RO mode. A malicious user could exploit this, and this ioctl does not even requires that a user has admin privileges (CAP_SYS_ADMIN), only that he/she owns the subvolume.
Fix this by doing an early check for item overflow before starting a transaction. This is also race safe because we are holding the subvol_sem semaphore in exclusive (write) mode.
A test case for fstests will follow soon.
From the CVE record · Linux
The Linux kernel’s btrfs set received ioctl can hit an item overflow when the same received UUID is used for many subvolumes, causing a transaction abort and turning the filesystem read-only. A local user can trigger this if they own the affected subvolumes; CAP_SYS_ADMIN is not required.
Engineers running Linux systems with btrfs should check their kernel versions; affected versions were not specified.