Menu

Star on GitHub · 3.2k

CVE-2022-50669

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(),…

Published Dec 9, 2025EPSS 0.25%

Overview

CVE-2022-50669 is a known-severity vulnerability. It was published on December 9, 2025.

Technical 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().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50669?

CVE-2022-50669 is a known-severity vulnerability. It was published on December 9, 2025.

How severe is CVE-2022-50669?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50669?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50669?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50669 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.