CVE-2026-99756
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_io…
Impact
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 products · Linux
| Product | Affected versions |
|---|---|
| Linux | from 949964c928430a42e0d4f514d888a58a201b6fcb before db399899dbac590d7d124b6896bd113916e7ab09 from 949964c928430a42e0d4f514d888a58a201b6fcb before 1960146913b31b288ed2cd607d103ee3b41681d4 Versions 5.7, patch: 7.4-rc2, patch: 0, patch: 7.3.5 |