CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5ef3961682e5310f2221bae99bcf9f5d0f4b0d51, 7dd6a5b96157a21245566b21fd58276a214357ff, 8a69529f22590b67bb018de9acbcf94abc8603cf.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 5ef3961682e5310f2221bae99bcf9f5d0f4b0d51, 7dd6a5b96157a21245566b21fd58276a214357ff, 8a69529f22590b67bb018de9acbcf94abc8603cf or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix quota root leak after quota disable failure If during the quota disable we fail when cleaning the quota tree or when deleting the root from the root tree, we jump to the 'out' label without ever dropping the reference on the quota root, resulting in a leak of the root since fs_info->quota_root is no longer pointing to the root (we have set it to NULL just before those steps). Fix this by always doing a btrfs_put_root() call under the 'out' label. This is a problem that exists since qgroups were first added in 2012 by commit bed92eae26cc ("Btrfs: qgroup implementation and prototypes"), but back then we missed a kfree on the quota root and free_extent_buffer() calls on its root and commit root nodes, since back then roots were not yet reference counted.
- Published
- Jul 29, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.6affected
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before 94818bdb00ef34a996a06aa63d11f591074cb757affected · git
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before 8a69529f22590b67bb018de9acbcf94abc8603cfaffected · git
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before 5ef3961682e5310f2221bae99bcf9f5d0f4b0d51affected · git
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before f88aeff5a173e8ba3133314eb4b964236ef3589daffected · git
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before 7dd6a5b96157a21245566b21fd58276a214357ffaffected · git
- bed92eae26ccf280d1a2168b7509447b56675a27 and later · before a7e4c6a3031c74078dba7fa36239d0f4fe476c53affected · git
- before 3.6not affected · semver
- 5.10.223 and later · up to and including 5.10.*not affected · semver
- 5.15.164 and later · up to and including 5.15.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10.223
- linux linux kernel5.11 and later · before 5.15.164
- linux linux kernel5.16 and later · before 6.1.101
- linux linux kernel6.2 and later · before 6.6.42
- linux linux kernel6.7 and later · before 6.9.11
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.9.11-1 | 6.9.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-41076Jul 29, 2024 · NFSv4: Fix memory leak in nfs4_set_security_label22Monitor
- ← EarlierCVE-2024-41077Jul 29, 2024 · null_blk: fix validation of block size22Monitor
- Later →CVE-2024-41079Jul 29, 2024 · nvmet: always initialize cqe.result22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5ef3961682e5310f2221bae99bcf9f5d0f4b0d51 | Vendor (CNA) |
| Linux Linux | 7dd6a5b96157a21245566b21fd58276a214357ff | Vendor (CNA) |
| Linux Linux | 8a69529f22590b67bb018de9acbcf94abc8603cf | Vendor (CNA) |
| Linux Linux | 94818bdb00ef34a996a06aa63d11f591074cb757 | Vendor (CNA) |
| Linux Linux | a7e4c6a3031c74078dba7fa36239d0f4fe476c53 | Vendor (CNA) |
| Linux Linux | f88aeff5a173e8ba3133314eb4b964236ef3589d | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1094 · Jul 30, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/7dd6a5b96157a21245566b21fd58276a214357ff
- git.kernel.org/stable/c/8a69529f22590b67bb018de9acbcf94abc8603cf
- git.kernel.org/stable/c/94818bdb00ef34a996a06aa63d11f591074cb757
- git.kernel.org/stable/c/a7e4c6a3031c74078dba7fa36239d0f4fe476c53
- git.kernel.org/stable/c/f88aeff5a173e8ba3133314eb4b964236ef3589d
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.