# cifs: Fix memory leak when using fscache

CVE record · `CVE-2022-50107`

- **Identifiers:** `CVE-2022-50107`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Jun 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Jun 2025, 11:02 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: `0174ee9947bd0f24fee2794b35258960d108b7aa to before 7105b4047481bc2950fb767cff328d8b75292c0f` (git)
  - affected: `0174ee9947bd0f24fee2794b35258960d108b7aa to before ae497726cd090673a4d20ac725ccc2de8067a7a5` (git)
  - affected: `0174ee9947bd0f24fee2794b35258960d108b7aa to before c6f62f81b488d00afaa86bae26c6ce9ab12c709e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.18.18 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19.2 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0 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 cifs component is affected from version 5.17 until fixes in 5.18.18, 5.19.2 and 6.0. A memory leak when using fscache leaks a page reference. The source does not say what an attacker would need to trigger it. Upgrade to 5.18.18, 5.19.2, 6.0 or a later release.

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

## Timeline

- 18 Jun 2025, 11:02 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50107)
- 18 Jun 2025, 11:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50107)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/7105b4047481bc2950fb767cff328d8b75292c0f>
- <https://git.kernel.org/stable/c/ae497726cd090673a4d20ac725ccc2de8067a7a5>
- <https://git.kernel.org/stable/c/c6f62f81b488d00afaa86bae26c6ce9ab12c709e>

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

---

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