# btrfs: fix inode list leak during backref walking at find_parent_nodes()

CVE record · `CVE-2022-49913`

- **Identifiers:** `CVE-2022-49913`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `86d5f994425252d8a40e2184c94a2682ae8ecfbf to before 6a6731a0df8c47ecc703bd7bb73459df767051e0` (git)
  - affected: `86d5f994425252d8a40e2184c94a2682ae8ecfbf to before 61e06128113711df0534c404fb6bb528eb7d2332` (git)
  - affected: `86d5f994425252d8a40e2184c94a2682ae8ecfbf to before 222a3d533027b9492d5b7f5ecdc01a90f57bb5a9` (git)
  - affected: `86d5f994425252d8a40e2184c94a2682ae8ecfbf to before 83ea8c5b54d452a5769e605e3c5c687e8ca06d89` (git)
  - affected: `86d5f994425252d8a40e2184c94a2682ae8ecfbf to before 92876eec382a0f19f33d09d2c939e9ca49038ae5` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.14`
  - unaffected: `before 4.14` (semver)
  - unaffected: `5.4.224 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.154 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.78 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.8 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 1 May 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-49913](https://www.cve.org/CVERecord?id=CVE-2022-49913)
- [NVD: CVE-2022-49913](https://nvd.nist.gov/vuln/detail/CVE-2022-49913)

### References from the CNA

- <https://git.kernel.org/stable/c/6a6731a0df8c47ecc703bd7bb73459df767051e0>
- <https://git.kernel.org/stable/c/61e06128113711df0534c404fb6bb528eb7d2332>
- <https://git.kernel.org/stable/c/222a3d533027b9492d5b7f5ecdc01a90f57bb5a9>
- <https://git.kernel.org/stable/c/83ea8c5b54d452a5769e605e3c5c687e8ca06d89>
- <https://git.kernel.org/stable/c/92876eec382a0f19f33d09d2c939e9ca49038ae5>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49913>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49913/>. Everything for agents: <https://agentprime.io/llms.txt>.
