CVE-2026-99756: btrfs: prevent deleting the wrong subvolume by ID

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

btrfs: prevent deleting the wrong subvolume by ID

When deleting a subvolume by ID, btrfsioctlsnapdestroy() 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(RENAMEEXCHANGE) 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 Software

5 affected componentsFixes available
linux/kernel>=5.7.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required to trigger the incorrect deletion?

The operation must delete a Btrfs subvolume by ID while another concurrent actor renames subvolumes. The reported reproduction repeatedly exchanged the names of two subvolumes with renameat2(RENAME_EXCHANGE) during deletion.

2

What is the practical impact of a successful race?

A subvolume other than the one requested by ID can be deleted, while the requested subvolume remains intact. In the reported testing, the wrong subvolume was deleted in 9 of 14 independent tests.

3

How does the fix change behavior during concurrent renames?

The deletion path verifies under the parent directory lock that the resolved subvolume ID still matches the requested ID. If it does not match, it returns -EAGAIN so userspace can retry rather than treating the requested subvolume as nonexistent.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203