# f2fs: fix to do sanity check for inline inode

CVE record · `CVE-2022-49361`

- **Identifiers:** `CVE-2022-49361`
- **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: `fcc85a4d86b5018f08717160c89c0eb50afd1dca to before efdefbe8b7564602ab446474788225a1f2a323b5` (git)
  - affected: `fcc85a4d86b5018f08717160c89c0eb50afd1dca to before 7cfe2d43becaf76e562b9617d2c2d9b445f86761` (git)
  - affected: `fcc85a4d86b5018f08717160c89c0eb50afd1dca to before 11c1cd032df85df3c096a57a7f27d57819956e4a` (git)
  - affected: `fcc85a4d86b5018f08717160c89c0eb50afd1dca to before 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8` (git)
  - affected: `fcc85a4d86b5018f08717160c89c0eb50afd1dca to before 677a82b44ebf263d4f9a0cfbd576a6ade797a07b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.2`
  - unaffected: `before 4.2` (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-49361](https://www.cve.org/CVERecord?id=CVE-2022-49361)
- [NVD: CVE-2022-49361](https://nvd.nist.gov/vuln/detail/CVE-2022-49361)

### References from the CNA

- <https://git.kernel.org/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5>
- <https://git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761>
- <https://git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a>
- <https://git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8>
- <https://git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b>

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

---

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