LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50245: rapidio: fix possible UAF when kfifo_alloc() fails

In the Linux kernel, the following vulnerability has been resolved: rapidio: fix possible UAF when kfifo_alloc() fails If kfifo_alloc() fails in mport_cdev_open(), goto err_fifo and just free priv. But priv is still in the chdev->file_list, then list traversal may cause UAF. This fixes the following smatch warning: drivers/rapidio/devices/rio_mport_cdev.c:1930 mport_cdev_open() warn: '&priv->list' not removed from list

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50245 is a Linux kernel RapidIO mport character device bug. If an internal FIFO allocation fails during open, cleanup can leave a freed object on a list, creating use-after-free risk. The sources do not provide a CVSS score or confirmed business impact.

Executive priority

Treat as a targeted kernel maintenance item unless RapidIO is used in the environment. There is no sourced evidence of active exploitation or severity scoring, but kernel memory-safety issues should still be closed through normal patch cycles.

Technical view

In drivers/rapidio/devices/rio_mport_cdev.c, mport_cdev_open() may free priv after kfifo_alloc() failure while priv remains linked in chdev->file_list. Later list traversal may dereference freed memory. Kernel stable commits remove this unsafe state.

Likely exposure

Exposure is most relevant to Linux systems with RapidIO mport character device support present and reachable. The bundle lists Linux as affected, but does not define exploit prerequisites, required privileges, or distro-specific package status.

Exploitation context

The bundle does not report active exploitation, public weaponization, or KEV listing. The failure path depends on kfifo_alloc() failing during device open, but exploitability and practical impact are not characterized in the provided sources.

Researcher notes

Evidence is limited to the upstream Linux fix description and stable commit references. Key missing details include CVSS, CWE mapping, reachable attack surface, privilege requirements, and whether the bug is exploitable beyond denial of service or memory corruption risk.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50245 applicability.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems exposing RapidIO mport character devices.
  • Disable or avoid unused RapidIO support where operationally feasible.
  • Track distro backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory running kernel versions and vendor build identifiers.
  • Check whether RapidIO mport character device support is enabled.
  • Compare vendor kernel changelogs against the referenced stable commits.
  • Review device node exposure and access controls for RapidIO mport devices.
  • Confirm remediation through kernel package metadata or source patch presence.
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-50245 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
3Timeline events
0ADP providers
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6, e8de370188d098bb49483c287b44925957c3c9b6unaffected
LinuxLinux4.6, 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.