fsverity: Set S_VERITY only after rollback is no longer possible
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 10c13801ea38e4ced23c59052ce45acb07c5deda, Kernel c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b and Kernel 7.3.2.
In the Linux kernel, the following vulnerability has been resolved: fsverity: Set S_VERITY only after rollback is no longer possible Commit f77f281b6118 ("fsverity: use a hashtable to find the fsverity_info") changed the implementation of FS_IOC_ENABLE_VERITY to make concurrent reads start going through fsverity verification slightly earlier than they did before. Instead of it happening when enable_verity() calls fsverity_set_info(), it now happens when ->end_enable_verity() sets S_VERITY. However, ext4 and btrfs can roll back verity after they set S_VERITY, causing a use-after-free. Fix that by making ext4 and btrfs set S_VERITY only after rollback is no longer possible. On failure, don't roll back S_VERITY, but do roll back the filesystem-specific verity flag. Also update enable_verity() to handle any future instances of this bug more safely by warning and *not* freeing the fsverity_info. Finally, tweak some comments. Clarify one, and move information from another to its proper place in the comment for ->end_enable_verity().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=f77f281b61183a5c0b87e6a4d101c70bd32c1c79 <10c13801ea38e4ced23c59052ce45acb07c5deda, >=f77f281b61183a5c0b87e6a4d101c70bd32c1c79 <c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b | 10c13801ea38e4ced23c59052ce45acb07c5deda, c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b |
| linux-kernel: Kernel | >=7.0.0 <7.3.2 | 7.3.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket