In the Linux kernel, the following vulnerability has been resolved:
btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations
Create subvolume, create snapshot and delete subvolume all use
btrfs_subvolume_reserve_metadata() to reserve metadata for the changes
done to the parent subvolume's fs tree, which cannot be mediated in the
normal way via start_transaction. When quota groups (squota or qgroups)
are enabled, this reserves qgroup metadata of type PREALLOC. Once the
operation is associated to a transaction, we convert PREALLOC to
PERTRANS, which gets cleared in bulk at the end of the transaction.
However, the error paths of these three operations were not implementing
this lifecycle correctly. They unconditionally converted the PREALLOC to
PERTRANS in a generic cleanup step regardless of errors or whether the
operation was fully associated to a transaction or not. This resulted in
error paths occasionally converting this rsv to PERTRANS without calling
record_root_in_trans successfully, which meant that unless that root got
recorded in the transaction by some other thread, the end of the
transaction would not free that root's PERTRANS, leaking it. Ultimately,
this resulted in hitting a WARN in CONFIG_BTRFS_DEBUG builds at unmount
for the leaked reservation.
The fix is to ensure that every qgroup PREALLOC reservation observes the
following properties:
1. any failure before record_root_in_trans is called successfully
results in freeing the PREALLOC reservation.
2. after record_root_in_trans, we convert to PERTRANS, and now the
transaction owns freeing the reservation.
This patch enforces those properties on the three operations. Without
it, generic/269 with squotas enabled at mkfs time would fail in ~5-10
runs on my system. With this patch, it ran successfully 1000 times in a
row.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects Btrfs quota accounting during subvolume, snapshot, or deletion error paths. The documented impact is a leaked quota reservation and a debug-build warning at unmount, not a confirmed data-loss or privilege issue. Treat it as a reliability and maintenance patch priority for Btrfs quota users.
Executive priority
Schedule through normal kernel patch management, faster for production systems relying on Btrfs quotas. The available evidence supports low urgency: no known exploitation and a documented reliability impact, but kernel filesystem fixes should not be ignored.
Technical view
Btrfs subvolume operations could incorrectly convert qgroup PREALLOC reservations to PERTRANS before record_root_in_trans succeeded. If the root was not later recorded by another thread, transaction cleanup did not free the reservation. The fix makes failures before record_root_in_trans free PREALLOC, while successful transaction association transfers cleanup ownership.
Likely exposure
Linux systems using Btrfs with qgroups or squotas enabled are the plausible exposure. The bundle lists Linux kernel versions and stable commit references, but does not provide complete distribution-specific affected ranges beyond a Debian LTS advisory reference.
Exploitation context
The bundle does not indicate active exploitation, public exploit activity, KEV listing, or weaponized use. The described reproducer is a filesystem regression test with squotas enabled, failing intermittently before the patch and passing after it.
Researcher notes
Evidence is strongest for the upstream bug mechanics and fix lifecycle. CVSS, CWE, and concrete security impact are not provided. Affected-version data in the bundle is limited and should be mapped through kernel stable branches or distribution advisories before exposure reporting.
Mitigation direction
Apply the relevant Linux stable kernel update containing the referenced Btrfs fix.
Prioritize hosts using Btrfs with qgroups or squotas enabled.
Check vendor or distribution advisories for exact package versions.
Avoid direct kernel cherry-picks unless standard kernel maintenance supports them.
Validation and detection
Inventory Linux systems using Btrfs filesystems.
Check whether qgroups or squotas are enabled on those filesystems.
Confirm the running kernel includes the referenced stable fix.
Review distribution advisories, including Debian LTS where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35956 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.