LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50199: ARM: OMAP2+: Fix refcount leak in omapdss_init_of

In the Linux kernel, the following vulnerability has been resolved: ARM: OMAP2+: Fix refcount leak in omapdss_init_of omapdss_find_dss_of_node() calls of_find_compatible_node() to get device node. of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() in later error path and normal path.

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-50199 is a Linux kernel bug in ARM OMAP2+ display initialization. The kernel can keep an extra reference to a device-tree node instead of releasing it. The public sources do not provide CVSS, impact scope, or a named exploit outcome, so urgency should be based on affected asset presence.

Executive priority

Handle through normal kernel maintenance unless your environment includes critical ARM OMAP2+ embedded devices. There is not enough public evidence to justify emergency action, but affected systems should not be left untracked.

Technical view

The issue is a reference-count leak in omapdss_init_of. omapdss_find_dss_of_node calls of_find_compatible_node, which returns a node pointer with an incremented reference count. The fix adds missing of_node_put calls on later error and normal paths.

Likely exposure

Exposure appears limited to Linux kernels using the ARM OMAP2+ display subsystem code path. The source lists affected Linux versions and stable kernel commits, but does not identify specific distributions, appliances, or cloud services.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit code, or attacker prerequisites. Treat exploitation likelihood as unconfirmed, not absent.

Researcher notes

The record describes a correctness fix for reference management, not a fully characterized security impact. No CWE, CVSS vector, exploitability details, or distribution-specific status are provided in the source bundle.

Mitigation direction

  • Update affected Linux kernels through vendor-supported packages or stable kernel releases.
  • Check whether vendor advisories map this CVE to your distribution or embedded kernel.
  • For maintained kernel trees, confirm the referenced stable commits are applied.
  • Prioritize business-critical ARM OMAP2+ embedded systems first.

Validation and detection

  • Inventory Linux assets using ARM OMAP2+ or related display subsystem code.
  • Compare running kernel versions and source trees against the affected versions and stable commits.
  • Review vendor kernel changelogs for CVE-2022-50199 or the referenced commit hashes.
  • Confirm omapdss_init_of releases the device-tree node on normal and error paths.
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-50199 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
7Source 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
LinuxLinuxe0c827aca0730b51f38081aa4e8ecf0912aab55f, e0c827aca0730b51f38081aa4e8ecf0912aab55f, e0c827aca0730b51f38081aa4e8ecf0912aab55f, e0c827aca0730b51f38081aa4e8ecf0912aab55f, e0c827aca0730b51f38081aa4e8ecf0912aab55f, e0c827aca0730b51f38081aa4e8ecf0912aab55funaffected
LinuxLinux4.20, 0, 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.