CVE-2022-49914: btrfs: fix inode list leak during backref walking at resolve_indirect_refs()
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.20% (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 2c0329406bb28109c07c6e23e5e3e0fa618a95d7, 396515db923ad5cbeb179d6b88927870b4cbebb7, 5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1.
Low priority for now. Upgrade to Linux Linux 2c0329406bb28109c07c6e23e5e3e0fa618a95d7, 396515db923ad5cbeb179d6b88927870b4cbebb7, 5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1 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: fix inode list leak during backref walking at resolve_indirect_refs() During backref walking, at resolve_indirect_refs(), if we get an error we jump to the 'out' label and call ulist_free() on the 'parents' ulist, which frees all the elements in the ulist - however that does not free any inode lists that may be attached to elements, through the 'aux' field of a ulist node, so we end up leaking lists if we have any attached to the unodes. Fix this by calling free_leaf_list() instead of ulist_free() when we exit from resolve_indirect_refs(). The static function free_leaf_list() is moved up for this to be possible and it's slightly simplified by removing unnecessary code.
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.5 and later · before 4.14.299
- linux linux kernel4.15 and later · before 4.19.265
- linux linux kernel4.20 and later · before 5.4.224
- linux linux kernel5.5 and later · before 5.10.154
- linux linux kernel5.11 and later · before 5.15.78
- linux linux kernel5.16 and later · before 6.0.8
- linux linux kernel6.1
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.5affected
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before b1dc9019bb5f89abae85645de1a2dd4830c1f8e9affected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before cded2c89774b99b67c98147ae103ea878c92a206affected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before 2c0329406bb28109c07c6e23e5e3e0fa618a95d7affected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before a52e24c7fcc3c5ce3588a14e3663c00868d36623affected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before 6ba3479f9e96b9ad460c7e77abc26dd16e5dec4faffected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before 396515db923ad5cbeb179d6b88927870b4cbebb7affected · git
- 3301958b7c1dae8f0f5ded63aa881e0b71e78464 and later · before 5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1affected · git
- before 3.5not affected · semver
- 4.14.299 and later · up to and including 4.14.*not affected · semver
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.0.8-1 | 6.0.8-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-2022-49912May 1, 2025 · btrfs: fix ulist leaks in error paths of qgroup self tests22Monitor
- ← EarlierCVE-2022-49913May 1, 2025 · btrfs: fix inode list leak during backref walking at find_parent_nodes()22Monitor
- Later →CVE-2022-49915May 1, 2025 · mISDN: fix possible memory leak in mISDN_register_device()22Monitor
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 | 2c0329406bb28109c07c6e23e5e3e0fa618a95d7 | Vendor (CNA) |
| Linux Linux | 396515db923ad5cbeb179d6b88927870b4cbebb7 | Vendor (CNA) |
| Linux Linux | 5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1 | Vendor (CNA) |
| Linux Linux | 6ba3479f9e96b9ad460c7e77abc26dd16e5dec4f | Vendor (CNA) |
| Linux Linux | a52e24c7fcc3c5ce3588a14e3663c00868d36623 | Vendor (CNA) |
| Linux Linux | b1dc9019bb5f89abae85645de1a2dd4830c1f8e9 | Vendor (CNA) |
| Linux Linux | cded2c89774b99b67c98147ae103ea878c92a206 | Vendor (CNA) |
| debian:linux | 6.0.8-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/396515db923ad5cbeb179d6b88927870b4cbebb7
- git.kernel.org/stable/c/5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1
- git.kernel.org/stable/c/6ba3479f9e96b9ad460c7e77abc26dd16e5dec4f
- git.kernel.org/stable/c/a52e24c7fcc3c5ce3588a14e3663c00868d36623
- git.kernel.org/stable/c/b1dc9019bb5f89abae85645de1a2dd4830c1f8e9
- git.kernel.org/stable/c/cded2c89774b99b67c98147ae103ea878c92a206
Vendor advisories and official records. Exploit/PoC links are deliberately left out.