CVE-2026-99756: Linux kernel · btrfs: prevent deleting the wrong subvolume by ID
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to db399899dbac590d7d124b6896bd113916e7ab09 or 1960146913b31b288ed2cd607d103ee3b41681d4 soon.
Data as of 20 Nov 2026, 06:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in db399899dbac590d7d124b6896bd113916e7ab09, 1960146913b31b288ed2cd607d103ee3b41681d4
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to db399899dbac590d7d124b6896bd113916e7ab09 or 1960146913b31b288ed2cd607d103ee3b41681d4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel commits db399899dbac590d7d124b6896bd113916e7ab09 and 1960146913b31b288ed2cd607d103ee3b41681d4. Users should update to a kernel version including these fixes. The patch ensures the subvolume ID is verified during deletion to prevent deleting the wrong subvolume. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's btrfs filesystem allows deletion of the wrong subvolume when deleting by ID due to a race condition involving concurrent renames. The issue arises because the deletion process resolves the subvolume ID to a name, then looks up the name again without verifying the ID, allowing a concurrent rename to cause the wrong subvolume to be deleted. This flaw was reproducible and fixed by adding an ID check under the parent directory lock to ensure the correct subvolume is deleted.