# f2fs: fix to clear dirty inode in f2fs_evict_inode()

CVE record · `CVE-2022-49364`

- **Identifiers:** `CVE-2022-49364`
- **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:** 15 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:11 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: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before 54c116615c99e22aa08aa950757ed726e2f60821` (git)
  - affected: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before ccd58045beb997544b94558a9156be4742628491` (git)
  - affected: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before c9196d21359be8c7ee231029d13682273925fd00` (git)
  - affected: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42` (git)
  - affected: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before c469953917b319d415fd621b9e5d0ea5203565cd` (git)
  - affected: `a11b9f65eae766b17ec3451a6a1766f0a9d1dbff to before f2db71053dc0409fae785096ad19cce4c8a95af7` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.10`
  - unaffected: `before 4.10` (semver)
  - unaffected: `5.4.198 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.121 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.46 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.14 to 5.17.*, inclusive` (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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th 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-49364](https://www.cve.org/CVERecord?id=CVE-2022-49364)
- [NVD: CVE-2022-49364](https://nvd.nist.gov/vuln/detail/CVE-2022-49364)

### References from the CNA

- <https://git.kernel.org/stable/c/54c116615c99e22aa08aa950757ed726e2f60821>
- <https://git.kernel.org/stable/c/ccd58045beb997544b94558a9156be4742628491>
- <https://git.kernel.org/stable/c/c9196d21359be8c7ee231029d13682273925fd00>
- <https://git.kernel.org/stable/c/03c9373b15fa1c245ec99b2b5e7ba209eae4ef42>
- <https://git.kernel.org/stable/c/c469953917b319d415fd621b9e5d0ea5203565cd>
- <https://git.kernel.org/stable/c/f2db71053dc0409fae785096ad19cce4c8a95af7>

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

---

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