LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2022-50669 is a Linux kernel issue in the ocxl driver where an allocated device name may not be freed after a registration failure. The described impact is a resource leak, not direct data theft or code execution. No source provided indicates active exploitation.

Executive priority

Treat as routine kernel maintenance unless your environment depends on ocxl/OpenCAPI hardware. There is no provided evidence of active exploitation or high-impact compromise, but kernel fixes should still be included in normal patch cycles.

Technical view

The flaw is in ocxl_file_register_afu(). If device_register() fails after dev_set_name(), the error path should release the device reference with put_device(), allowing kobject_cleanup() and info_release() to free allocated state. Upstream stable commits implement this cleanup behavior.

Likely exposure

Exposure is most relevant to Linux systems using kernels with the ocxl driver code, especially environments using OpenCAPI/accelerator functionality. The provided record does not define a precise exploit prerequisite, attack vector, or distro-specific package list.

Exploitation context

The source bundle marks CISA KEV as false and provides no cited evidence of public exploitation. The described condition depends on a device registration error path, suggesting reliability or resource exhaustion risk rather than an immediately demonstrated compromise path.

Researcher notes

The CVE record lacks CVSS, CWE, and detailed affected-version semantics. Analysis should focus on the upstream commit behavior and distro backports. Avoid assuming exploitability beyond the documented memory/name leak on the device_register() failure path.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2022-50669 applicability.
  • Update to a kernel containing the referenced upstream stable fix.
  • Prioritize systems using ocxl/OpenCAPI functionality if present.
  • If ocxl is unnecessary, evaluate disabling it using vendor-supported guidance.

Validation and detection

  • Inventory kernel versions and enabled ocxl driver usage.
  • Compare installed kernel source or package changelog against referenced stable commits.
  • Confirm vendor kernel advisory status for affected distributions.
  • Monitor for unusual kernel resource leaks on relevant systems.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50669 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux75ca758adbafc81804c39b2c200ecdc819a6c042, 75ca758adbafc81804c39b2c200ecdc819a6c042, 75ca758adbafc81804c39b2c200ecdc819a6c042, 75ca758adbafc81804c39b2c200ecdc819a6c042, 75ca758adbafc81804c39b2c200ecdc819a6c042, 75ca758adbafc81804c39b2c200ecdc819a6c042unaffected
LinuxLinux5.2, 0, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.