# CVE-2022-50669: misc: ocxl: fix possible name leak in ocxl_file_register_afu()

> A memory leak in the Linux kernel OCXL driver allows local attackers to potentially read sensitive kernel memory or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50669, GHSA-ffpg-m95f-r6q9, UBUNTU-CVE-2022-50669

## What is CVE-2022-50669?

CVE-2022-50669 is a memory corruption vulnerability in Linux, published on 9 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:

misc: ocxl: fix possible name leak in ocxl_file_register_afu()

If device_register() returns error in ocxl_file_register_afu(),
the name allocated by dev_set_name() need be freed. As comment
of device_register() says, it should use put_device() to give
up the reference in the error path. So fix this by calling
put_device(), then the name can be freed in kobject_cleanup(),
and info is freed in info_release().

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


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

Apply the vendor's patch.

## Is CVE-2022-50669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50669 is a memory corruption vulnerability in Linux, published on 9 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-50669 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-50669/ (Markdown: https://insights.sbomify.com/CVE-2022-50669/index.md)
```

## Sources

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

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