# CVE-2022-50785: fsi: occ: Prevent use after free

> A use-after-free vulnerability in the Linux kernel FSI OCC driver allows attackers to potentially execute code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50785, GHSA-wv6p-qh73-f5xp, ROOT-OS-UBUNTU-2204-CVE-2022-50785, UBUNTU-CVE-2022-50785

## What is CVE-2022-50785?

CVE-2022-50785 is a high-severity use after free vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

fsi: occ: Prevent use after free

Use get_device and put_device in the open and close functions to
make sure the device doesn't get freed while a file descriptor is
open.
Also, lock around the freeing of the device buffer and check the
buffer before using it in the submit function.

## Which versions are affected by CVE-2022-50785?


## How do I fix CVE-2022-50785?

Apply the vendor's patch.

## Is CVE-2022-50785 being exploited?

There is no known exploitation of CVE-2022-50785 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50785 and fix it if it is affected.

What it is: CVE-2022-50785 is a high-severity use after free vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50785 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50785/ (Markdown: https://insights.sbomify.com/CVE-2022-50785/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50785
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50785
- OSV: https://osv.dev/vulnerability/CVE-2022-50785

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50785/
Summaries are generated and may contain mistakes; the official description above is the record.