# btrfs: fix hang during unmount when stopping a space reclaim worker

CVE record · `CVE-2022-48664`

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

Published by the CVE Program (CNA: Linux) at 28 Apr 2024, 13:01 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: `d6fd0ae25c6495674dc5a41a8d16bc8e0073276d to before 6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8` (git)
  - affected: `d6fd0ae25c6495674dc5a41a8d16bc8e0073276d to before d8a76a2e514fbbb315a6dfff2d342de2de833994` (git)
  - affected: `d6fd0ae25c6495674dc5a41a8d16bc8e0073276d to before c338bea1fec5504290dc0acf026c9e7dba25004b` (git)
  - affected: `d6fd0ae25c6495674dc5a41a8d16bc8e0073276d to before a362bb864b8db4861977d00bd2c3222503ccc34b` (git)
  - affected: `1ec2bf44c3770b9c3d510b1e78d50cd7fd19e8c5` (git)
  - affected: `b4c7c826709b7d882ec9b264d5032e887e6bd720` (git)
  - affected: `4.14.120 to before 4.15` (semver)
  - affected: `4.19.12 to before 4.20` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.20`
  - unaffected: `before 4.20` (semver)
  - unaffected: `5.10.147 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.71 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.12 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0 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.0024, the 14th percentile, on 21 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 28 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8>
- <https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994>
- <https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b>
- <https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b>

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

---

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