cveboard RSS feed

CVE-2024-35956

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2024
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
e85fde5162bf1b242cbd6daf7dba0f9b457d592baffectedgit945559be6e282a812dc48f7bcd5adc60901ea4a0UnavailableNone listed
e85fde5162bf1b242cbd6daf7dba0f9b457d592baffectedgit14431815a4ae4bcd7c7a68b6a64c66c7712d27c9UnavailableNone listed
e85fde5162bf1b242cbd6daf7dba0f9b457d592baffectedgit6c95336f5d8eb9ab79cd7306d71b6d0477363f8cUnavailableNone listed
e85fde5162bf1b242cbd6daf7dba0f9b457d592baffectedgit74e97958121aa1f5854da6effba70143f051b0cdUnavailableNone listed
2978cb474745b2d93c263008d265e89985706094affectedgitUnavailableUnavailableNone listed
5.9.5affectedsemver5.10UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.10affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.10UnavailableNone listed
6.1.120unaffectedsemverUnavailable6.1.*None listed
6.6.28unaffectedsemverUnavailable6.6.*None listed
6.8.7unaffectedsemverUnavailable6.8.*None listed
6.9unaffectedoriginal_commit_for_fixUnavailable*None listed