# cachefiles: unmark inode in use in error path

CVE record · `CVE-2022-49064`

- **Identifiers:** `CVE-2022-49064`
- **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:** 5 Nov 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: `1f08c925e7a38002bde509e66f6f891468848511 to before b2055abafd3d4ee0376fb3eed5cae866316995a1` (git)
  - affected: `1f08c925e7a38002bde509e66f6f891468848511 to before ea5dc046127e857a7873ae55fd57c866e9e86fb2` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.17.4 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's cachefiles subsystem (CVE-2022-49064) can leak an inode in-use flag in its error paths, so a later lookup of a cookie with the same index key triggers an "Inode already in use" complaint. The source gives few details about the impact beyond this warning. The affected range is listed as Linux 5.17 before 5.17.4 and certain earlier commits, with 5.17.4 and later and 5.18 and later unaffected. The source does not describe a fix version to upgrade to beyond those listed; no workaround is given.

Written 16 Nov 2026.

## 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.0022, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 01:54 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49064)
- 26 Feb 2025, 07:00 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49064)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/b2055abafd3d4ee0376fb3eed5cae866316995a1>
- <https://git.kernel.org/stable/c/ea5dc046127e857a7873ae55fd57c866e9e86fb2>

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

---

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