CVE-2022-49913btrfs: fix inode list leak during backref walking at find_parent_nodes()
- 5.5MediumCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix inode list leak during backref walking at find_parent_nodes() During backref walking, at find_parent_nodes(), if we are dealing with a data extent and we get an error while resolving the indirect backrefs, at resolve_indirect_refs(), or in the while loop that iterates over the refs in the direct refs rbtree, we end up leaking the inode lists attached to the direct refs we have in the direct refs rbtree that were not yet added to the refs ulist passed as argument to find_parent_nodes(). Since they were not yet added to the refs ulist and prelim_release() does not free the lists, on error the caller can only free the lists attached to the refs that were added to the refs ulist, all the remaining refs get their inode lists never freed, therefore leaking their memory. Fix this by having prelim_release() always free any attached inode list to each ref found in the rbtree, and have find_parent_nodes() set the ref's inode list to NULL once it transfers ownership of the inode list to a ref added to the refs ulist passed to find_parent_nodes().
Timeline
ID reserved
By Linux
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 86d5f994425252d8a40e2184c94a2682ae8ecfbf – < 6a6731a0df8c47ecc703bd7bb73459df767051e0
- affected 86d5f994425252d8a40e2184c94a2682ae8ecfbf – < 61e06128113711df0534c404fb6bb528eb7d2332
- affected 86d5f994425252d8a40e2184c94a2682ae8ecfbf – < 222a3d533027b9492d5b7f5ecdc01a90f57bb5a9
- affected 86d5f994425252d8a40e2184c94a2682ae8ecfbf – < 83ea8c5b54d452a5769e605e3c5c687e8ca06d89
- affected 86d5f994425252d8a40e2184c94a2682ae8ecfbf – < 92876eec382a0f19f33d09d2c939e9ca49038ae5
- affected 4.14
- unaffected < 4.14
- unaffected 5.4.224 – ≤ 5.4.*
- unaffected 5.10.154 – ≤ 5.10.*
- unaffected 5.15.78 – ≤ 5.15.*
- unaffected 6.0.8 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/6a6731a0df8c47ecc703bd7bb73459df767051e0 (opens in a new tab)
- https://git.kernel.org/stable/c/61e06128113711df0534c404fb6bb528eb7d2332 (opens in a new tab)
- https://git.kernel.org/stable/c/222a3d533027b9492d5b7f5ecdc01a90f57bb5a9 (opens in a new tab)
- https://git.kernel.org/stable/c/83ea8c5b54d452a5769e605e3c5c687e8ca06d89 (opens in a new tab)
- https://git.kernel.org/stable/c/92876eec382a0f19f33d09d2c939e9ca49038ae5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-12854 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49913)Record last updated .