LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50857: rapidio: rio: fix possible name leak in rio_register_mport()

In the Linux kernel, the following vulnerability has been resolved: rapidio: rio: fix possible name leak in rio_register_mport() If device_register() returns error, the name allocated by dev_set_name() need be freed. It should use put_device() to give up the reference in the error path, so that the name can be freed in kobject_cleanup(), and list_del() is called to delete the port from rio_mports.

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-50857 is a Linux kernel cleanup bug in the RapidIO subsystem. If a port registration fails, the kernel may not release an allocated device name and may leave list cleanup incomplete. The public record does not show active exploitation, CVSS scoring, or broad business impact.

Executive priority

Treat as routine kernel hygiene unless your environment depends on RapidIO-enabled Linux systems. Patch through normal kernel update cycles, with higher priority for embedded, telecom, or specialized hardware using RapidIO.

Technical view

The flaw is in rio_register_mport(). When device_register() returns an error after dev_set_name(), the error path should call put_device() so kobject_cleanup() frees the allocated name and list_del() removes the port from rio_mports. Kernel stable commits implement this cleanup correction.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds where RapidIO support is present or used. The source lists Linux kernel versions and stable fix commits, but distro-specific affected package mapping must be confirmed through vendor advisories.

Exploitation context

No KEV listing is present, and the provided sources do not report active exploitation or public exploit activity. The described impact is a resource/name leak and cleanup inconsistency on an error path, not a documented privilege escalation or remote code execution issue.

Researcher notes

The record lacks CVSS, CWE, exploitability detail, and distro package mapping. Analysis should focus on kernel version ancestry and whether the RapidIO driver path is compiled, loaded, or reachable in the target environment.

Mitigation direction

  • Update to a kernel build containing the referenced stable fix commits.
  • Use your Linux distribution’s advisory to identify the corrected package version.
  • Prioritize systems with RapidIO support enabled or relevant hardware exposure.
  • If patch timing is constrained, monitor vendor guidance for supported workarounds.

Validation and detection

  • Inventory Linux kernel versions across affected server, appliance, and embedded fleets.
  • Check whether RapidIO support is enabled or relevant on those systems.
  • Map running kernels to distro advisories or upstream stable fix commits.
  • Confirm updated kernels are deployed and active after maintenance windows.
Prepared
Confidence
medium
Sources
11

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-50857 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
10Source 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
LinuxLinux2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2a, 2aaf308b95b24649a6dcfed89cd956e972089b2aunaffected
LinuxLinux3.15, 0, 4.9.337, 4.14.303, 4.19.270, 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.