In the Linux kernel, the following vulnerability has been resolved:
video: fbdev: amba-clcd: Fix refcount leak bugs
In clcdfb_of_init_display(), we should call of_node_put() for the
references returned by of_graph_get_next_endpoint() and
of_graph_get_remote_port_parent() which have increased the refcount.
Besides, we should call of_node_put() both in fail path or when
the references are not used anymore.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50109 is a Linux kernel bug in the AMBA CLCD framebuffer display driver. The published description says some device-tree node references were not released correctly, causing reference-count leaks. Business impact is unclear because no CVSS score, CWE, or exploitation evidence is provided.
Executive priority
Track and remediate through normal kernel patch management unless your environment uses AMBA CLCD framebuffer systems. Escalate only if vendor guidance identifies higher impact or exposed operational assets.
Technical view
The issue is in clcdfb_of_init_display() under video/fbdev/amba-clcd. References returned by of_graph_get_next_endpoint() and of_graph_get_remote_port_parent() increment refcounts and should be released with of_node_put() on success and failure paths.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions with the AMBA CLCD framebuffer driver and relevant device-tree display configuration. General Linux fleets may not be exposed if this driver is absent, disabled, or unused.
Exploitation context
The source bundle does not report active exploitation, public exploit use, KEV listing, CVSS, or a concrete impact scenario. Treat exploitability and operational impact as unconfirmed from the available evidence.
Researcher notes
Evidence identifies a reference-count leak fix, not a described privilege escalation or remote attack. The record lacks CVSS, CWE, and impact detail, so analysis should stay bounded to the driver and affected Linux versions listed.
Mitigation direction
Check distro or kernel vendor advisories for backported fixes.
Update affected kernels to releases containing the referenced stable commits.
Prioritize systems using AMBA CLCD framebuffer hardware or configuration.
Document exceptions where the driver is absent, disabled, or unused.
Validation and detection
Inventory kernel versions against the affected version list.
Confirm whether the amba-clcd framebuffer driver is built, loaded, or configured.
Review vendor package changelogs for the referenced stable fixes.
Check device-tree usage for AMBA CLCD display endpoints.
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-50109 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.