btrfs: prevent deleting the wrong subvolume by ID
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1960146913b31b288ed2cd607d103ee3b41681d4, Kernel db399899dbac590d7d124b6896bd113916e7ab09 and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: btrfs: prevent deleting the wrong subvolume by ID When deleting a subvolume by ID, btrfs_ioctl_snap_destroy() first resolves the requested ID to a name, then looks up that name again under the parent directory lock. A concurrent rename can change which subvolume is associated with the name between these operations. Since the deletion path does not verify the ID of the resolved subvolume, it can delete a different subvolume while leaving the requested one intact. This was reproduced by repeatedly exchanging the names of two subvolumes using renameat2(RENAME_EXCHANGE) while deleting one of them by ID. The wrong subvolume was deleted in 9 out of 14 independent tests. Fix this by checking that the resolved subvolume ID matches the requested ID while holding the parent directory lock. Return -EAGAIN on a mismatch so that userspace can retry the operation instead of being told that the requested subvolume does not exist.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.7, >=949964c928430a42e0d4f514d888a58a201b6fcb <1960146913b31b288ed2cd607d103ee3b41681d4, >=949964c928430a42e0d4f514d888a58a201b6fcb <db399899dbac590d7d124b6896bd113916e7ab09 | 1960146913b31b288ed2cd607d103ee3b41681d4, db399899dbac590d7d124b6896bd113916e7ab09 |
| linux-kernel: Kernel | >=5.7.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket