# NFS: Avoid writeback threads getting stuck in mempool_alloc()

CVE record · `CVE-2022-49097`

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

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 01:54 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: `2b17d725f9be59a1bfa0583af690c463fca1f385 to before c74e2f6ecc51bd08bb5b0335477dba954a50592e` (git)
  - affected: `2b17d725f9be59a1bfa0583af690c463fca1f385 to before ea029e4ce760f786919d06ef52efa2e50ea92a5f` (git)
  - affected: `2b17d725f9be59a1bfa0583af690c463fca1f385 to before 1b3fa9a3c420c31e77b406ddc28f3a627100516c` (git)
  - affected: `2b17d725f9be59a1bfa0583af690c463fca1f385 to before a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3` (git)
  - affected: `2b17d725f9be59a1bfa0583af690c463fca1f385 to before 0bae835b63c53f86cdc524f5962e39409585b22c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.3`
  - unaffected: `before 5.3` (semver)
  - unaffected: `5.10.111 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.34 to 5.15.*, inclusive` (semver)
  - unaffected: `5.16.20 to 5.16.*, inclusive` (semver)
  - unaffected: `5.17.3 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18 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.0025, the 17th 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 26 Feb 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/c74e2f6ecc51bd08bb5b0335477dba954a50592e>
- <https://git.kernel.org/stable/c/ea029e4ce760f786919d06ef52efa2e50ea92a5f>
- <https://git.kernel.org/stable/c/1b3fa9a3c420c31e77b406ddc28f3a627100516c>
- <https://git.kernel.org/stable/c/a6caeddd68977a1aaaf62fbd1955b41dd5c3c5d3>
- <https://git.kernel.org/stable/c/0bae835b63c53f86cdc524f5962e39409585b22c>

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

---

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