btrfs: abort transaction on failure to update inode for hole punching and reflinking
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: abort transaction on failure to update inode for hole punching and reflinking
If we fail to update the inode we error out without aborting the transaction, which can result in a persistent inconsistency if after the failure the transaction is committed, as we have dropped file extent items from a range and either punched a hole or insert a new file extent item for that range (for reflinks).
So add the missing transaction abort.
From the CVE record · Linux
A btrfs error path can leave a transaction un-aborted when an inode update fails during hole punching or reflinking. If that transaction is then committed, it can cause a persistent inconsistency. The input does not specify attacker access requirements or whether user interaction is needed.
Operators running Linux kernels with btrfs should check their versions; affected versions are not specified.