# btrfs: fix deadlock between concurrent dio writes when low on free data space

CVE record · `CVE-2022-49547`

- **Identifiers:** `CVE-2022-49547`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-667](https://cwe.mitre.org/data/definitions/667.html)
- **Tags:** [CWE-667](https://agentprime.io/advisories/tag/cwe-667.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 23 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:13 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: `f0bfa76a11e93d0fe2c896fcb566568c5e8b5d3f to before cfae6f765b3c40882ee90dae8fbf9325c8de9c35` (git)
  - affected: `f0bfa76a11e93d0fe2c896fcb566568c5e8b5d3f to before f5585f4f0ef5b17026bbd60fbff6fcc91b99d5bf` (git)
  - affected: `5afd80c393f4e87451f14eefb7f2f24daf434e06` (git)
  - affected: `96f1be29492d9e2fb97bb27f824478ab8cd3ab86` (git)
  - affected: `5.15.27 to before 5.16` (semver)
  - affected: `5.16.13 to before 5.17` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 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

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 5 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 26 Feb 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/cfae6f765b3c40882ee90dae8fbf9325c8de9c35>
- <https://git.kernel.org/stable/c/f5585f4f0ef5b17026bbd60fbff6fcc91b99d5bf>

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-49547>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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