{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-99756","id":"CVE-2026-99756","title":"Linux kernel unintended subvolume deletion in btrfs deletion by ID","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: prevent deleting the wrong subvolume by ID\n\nWhen deleting a subvolume by ID, btrfs_ioctl_snap_destroy() first\nresolves the requested ID to a name, then looks up that name again\nunder the parent directory lock.\n\nA concurrent rename can change which subvolume is associated with\nthe name between these operations. Since the de","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: prevent deleting the wrong subvolume by ID\n\nWhen deleting a subvolume by ID, btrfs_ioctl_snap_destroy() first\nresolves the requested ID to a name, then looks up that name again\nunder the parent directory lock.\n\nA concurrent rename can change which subvolume is associated with\nthe name between these operations. Since the deletion path does not\nverify the ID of the resolved subvolume, it can delete a different\nsubvolume while leaving the requested one intact.\n\nThis was reproduced by repeatedly exchanging the names of two\nsubvolumes using renameat2(RENAME_EXCHANGE) while deleting one of\nthem by ID. The wrong subvolume was deleted in 9 out of 14 independent\ntests.\n\nFix this by checking that the resolved subvolume ID matches the\nrequested ID while holding the parent directory lock. Return -EAGAIN\non a mismatch so that userspace can retry the operation instead of\nbeing told that the requested subvolume does not exist.","published":"2026-11-20T05:51:25.263Z","updated":"2026-11-20T07:01:03.809567062Z","reserved":"2026-09-25T10:25:14.432Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"949964c928430a42e0d4f514d888a58a201b6fcb","lessThan":"db399899dbac590d7d124b6896bd113916e7ab09","status":"affected","versionType":"git"},{"version":"949964c928430a42e0d4f514d888a58a201b6fcb","lessThan":"1960146913b31b288ed2cd607d103ee3b41681d4","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.7","status":"affected"},{"version":"0","lessThan":"5.7","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/db399899dbac590d7d124b6896bd113916e7ab09","tags":["web"]},{"url":"https://git.kernel.org/stable/c/1960146913b31b288ed2cd607d103ee3b41681d4","tags":["web"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99756.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99756","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":null,"epssPercentile":null,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-99756","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99756","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-99756","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-99756","ok":false,"note":"no score yet"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}