LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50203: ARM: OMAP2+: display: Fix refcount leak bug

In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: display: Fix refcount leak bug In omapdss_init_fbdev(), of_find_node_by_name() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.

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

Security readout for executives and security teams

Plain-English summary

This CVE covers a Linux kernel bug in the ARM OMAP2+ display code. A device-tree node reference is not released after use, causing a reference-count leak. The provided sources do not describe data theft, privilege escalation, remote access, or service outage impact.

Executive priority

Treat as routine kernel maintenance unless your environment depends on ARM OMAP2+ display systems. The provided evidence does not support emergency response, but affected embedded devices should receive vendor-supported kernel updates.

Technical view

In omapdss_init_fbdev(), of_find_node_by_name() increments a device-tree node reference count. The fix adds the missing release with of_node_put() when the node is no longer needed. The affected area is Linux kernel ARM OMAP2+ display support.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with ARM OMAP2+ display support. The supplied data lists Linux as affected but does not provide CPEs, distributions, or deployment-specific reachability conditions.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. No exploit prerequisites, attack vector, or security impact are described beyond the kernel refcount leak.

Researcher notes

The public description is narrow: missing of_node_put() after of_find_node_by_name() in omapdss_init_fbdev(). Severity, CWE, CVSS, exploitability, and concrete impact are not supplied, so further analysis should start from the linked kernel commits.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution or device vendor advisories for backported fixes.
  • Prioritize embedded ARM OMAP2+ systems with display support enabled.
  • Track remediation through normal kernel lifecycle management.

Validation and detection

  • Inventory devices running Linux on ARM OMAP2+ platforms.
  • Confirm whether OMAP display or fbdev support is present.
  • Compare deployed kernel versions against vendor-fixed builds.
  • Verify vendor kernel packages include the referenced stable commits.
Prepared
Confidence
medium
Sources
10

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-50203 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
9Source 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
LinuxLinux23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008, 23d34981c7e36fb609d3eaacf0a52a05d75ae008unaffected
LinuxLinux4.1, 0, 4.14.291, 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.