UNKNOWNCVSS not yet scoredVulnerability

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_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.

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00156
Cve id
CVE-2026-99756
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99756
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T06:18:13.827
Last modified
2026-11-20T06:18:13.827
Epss percentile
0.04724

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99756 — Ninja Signal Threat Intelligence | Ninja Signal