CVE-2022-49421: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup
In the Linux kernel, the following vulnerability has been resolved:
video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup
of_parse_phandle() 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.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49421 is a Linux kernel bug in the CLCD framebuffer driver. The bug leaks a device-tree node reference during video memory setup. Public sources describe it as fixed, but provide no CVSS score or evidence of exploitation. Business urgency is generally limited unless you operate affected Linux kernels on systems using this framebuffer driver.
Executive priority
Track and remediate through normal kernel maintenance. Escalate only for fleets of embedded or ARM Linux devices using this display driver. There is no cited evidence of active exploitation or broad internet-exposed risk in the provided sources.
Technical view
The issue is in video/fbdev/clcdfb, function clcdfb_of_vram_setup. of_parse_phandle() increments a node reference count, but the code failed to call of_node_put() when done. The upstream fix adds the missing release to avoid a refcount leak. The CVE record lists Linux kernel versions as affected and links multiple stable backport commits.
Likely exposure
Most exposure is likely on Linux systems using the ARM CLCD framebuffer driver and relevant device-tree video memory configuration. Servers and cloud workloads without this driver or hardware path are less likely to be exposed. The provided sources do not identify affected distributions, appliances, or default configurations.
Exploitation context
No provided source reports active exploitation, public weaponization, or inclusion in CISA KEV. The described impact is a kernel reference-count leak, which may cause resource leakage over time if the affected path is exercised. Practical impact depends on driver availability and runtime conditions.
Researcher notes
The CVE evidence is narrow: a resolved Linux kernel refcount leak with stable backports. No CVSS, CWE, exploit status, or downstream distro mapping is provided. Research should focus on reachability of clcdfb_of_vram_setup in specific kernel builds and device-tree configurations, without assuming universal Linux exposure.
Mitigation direction
Apply Linux kernel updates that include the referenced stable commits.
Check distribution or device vendor advisories for packaged kernel fixes.
Prioritize embedded or ARM systems using the CLCD framebuffer driver.
If no vendor package is available, follow vendor kernel maintenance guidance.
Validation and detection
Inventory Linux kernel versions against the CVE record and vendor advisories.
Confirm whether the CLCD framebuffer driver is built, loaded, or used.
Review kernel changelogs for the referenced stable commit IDs.
Verify patched kernels are deployed on exposed devices.
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-49421 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
10Source 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.
Feb 26, 2025, 02:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.