{"api_version":"1","generated_at":"2026-11-20T07:30:04+00:00","cve":"CVE-2026-99756","urls":{"html":"https://cve.report/CVE-2026-99756","api":"https://cve.report/api/cve/CVE-2026-99756.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99756","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99756"},"summary":{"title":"btrfs: prevent deleting the wrong subvolume 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 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:13","updated_at":"2026-11-20 06:18:13"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/db399899dbac590d7d124b6896bd113916e7ab09","name":"https://git.kernel.org/stable/c/db399899dbac590d7d124b6896bd113916e7ab09","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1960146913b31b288ed2cd607d103ee3b41681d4","name":"https://git.kernel.org/stable/c/1960146913b31b288ed2cd607d103ee3b41681d4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99756","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99756","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 949964c928430a42e0d4f514d888a58a201b6fcb db399899dbac590d7d124b6896bd113916e7ab09 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 949964c928430a42e0d4f514d888a58a201b6fcb 1960146913b31b288ed2cd607d103ee3b41681d4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/btrfs/ioctl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"db399899dbac590d7d124b6896bd113916e7ab09","status":"affected","version":"949964c928430a42e0d4f514d888a58a201b6fcb","versionType":"git"},{"lessThan":"1960146913b31b288ed2cd607d103ee3b41681d4","status":"affected","version":"949964c928430a42e0d4f514d888a58a201b6fcb","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/btrfs/ioctl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.7"},{"lessThan":"5.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"5.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"5.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:25.263Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/db399899dbac590d7d124b6896bd113916e7ab09"},{"url":"https://git.kernel.org/stable/c/1960146913b31b288ed2cd607d103ee3b41681d4"}],"title":"btrfs: prevent deleting the wrong subvolume by ID","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99756","datePublished":"2026-11-20T05:51:25.263Z","dateReserved":"2026-09-25T10:25:14.432Z","dateUpdated":"2026-11-20T05:51:25.263Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:13","lastModifiedDate":"2026-11-20 06:18:13","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99756","Ordinal":"1","Title":"btrfs: prevent deleting the wrong subvolume by ID","CVE":"CVE-2026-99756","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99756","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"btrfs: prevent deleting the wrong subvolume by ID"}]}}}