LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50198: ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init

In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel resource leak in ARM OMAP3 initialization code. The described impact is a missed reference release, not a direct remote compromise. Business urgency is mainly for embedded or legacy ARM devices running affected kernels, especially where uptime and resource stability matter.

Executive priority

Track this as low-priority maintenance unless your organization operates ARM OMAP embedded devices. For exposed products, fold remediation into the next kernel maintenance cycle unless vendor guidance raises severity.

Technical view

The issue is in omap3xxx_prm_late_init. of_find_matching_node() increments a device-tree node reference count, but the code did not call of_node_put() when finished. The kernel stable fixes add the missing release to avoid a refcount leak.

Likely exposure

Exposure appears limited to Linux systems using ARM OMAP2/OMAP3 platform code on affected kernel versions. Typical cloud, workstation, and x86 server fleets are unlikely to be exposed unless they build or ship this ARM platform support.

Exploitation context

The source bundle does not show public exploitation, KEV listing, exploit code, or attacker prerequisites. It documents a kernel refcount leak fixed in stable kernel commits, so exploitation claims should not be made from the available evidence.

Researcher notes

Evidence supports a reference-count leak in a narrow ARM platform initialization path. No CVSS, CWE, or exploit detail is provided. Treat impact analysis as constrained until vendor advisories or downstream distro notes clarify affected configurations.

Mitigation direction

  • Inventory Linux kernels used in ARM OMAP2/OMAP3 embedded devices.
  • Apply vendor-supported kernel updates containing the referenced stable fixes.
  • Check Linux distribution or device vendor advisories for backported patches.
  • Prioritize long-running devices where resource leaks can affect stability.

Validation and detection

  • Confirm whether deployed kernels include ARM OMAP2/OMAP3 support.
  • Compare kernel version and vendor patch level against supplied CVE records.
  • Review kernel changelogs for the referenced stable commit identifiers.
  • Verify updated builds include the missing of_node_put() fix.
Prepared
Confidence
medium
Sources
9

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-50198 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
8Source 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
LinuxLinux1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6a, 1e037794f7f00ff464db446ace892dae84175a6aunaffected
LinuxLinux3.18, 0, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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