CVE-2022-50559: clk: imx: scu: fix memleak on platform_device_add() fails
In the Linux kernel, the following vulnerability has been resolved:
clk: imx: scu: fix memleak on platform_device_add() fails
No error handling is performed when platform_device_add()
fails. Add error processing before return, and modified
the return value.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50559 is a Linux kernel issue where an error path in the i.MX SCU clock driver can leak memory if platform_device_add() fails. The public record does not provide a CVSS score, exploitation evidence, or impact beyond the memory leak. Treat this mainly as a kernel maintenance and stability fix unless your environment depends on affected i.MX platforms.
Executive priority
Low urgency for most enterprises, but include it in regular kernel patch cycles. Raise priority for embedded, industrial, or appliance fleets based on NXP i.MX platforms where kernel stability and long uptimes are important.
Technical view
The resolved bug is in the Linux kernel clk: imx: scu code. When platform_device_add() fails, prior code did not perform error handling before returning, causing a memory leak and incorrect return handling. The provided references are stable kernel commits carrying the fix. The CVE data lists Linux kernel versions as affected but does not provide detailed exploitability conditions.
Likely exposure
Likely exposure is limited to Linux systems running affected kernel versions with the i.MX SCU clock driver relevant to their hardware. General-purpose servers not using that platform-specific driver are less likely to be meaningfully exposed. Distribution kernels may already include backported fixes, so version-only checks can be misleading.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked as CISA KEV. No public exploit details are included in the source bundle. The issue appears tied to an error path, so practical impact depends on whether that failure path can be reached in the target environment.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected ranges are provided. The strongest facts are the kernel commit description and stable fix references. Validation should focus on source-level patch presence and vendor backport status rather than assuming exposure from upstream version numbers alone.
Mitigation direction
Update to a kernel or vendor package that includes the referenced stable fixes.
Check your Linux distribution or device vendor advisory for backported patches.
Prioritize embedded or appliance systems using NXP i.MX SCU-related kernels.
If no vendor fix is available, monitor vendor guidance and plan kernel maintenance.
Validation and detection
Inventory Linux kernel versions and hardware platforms in scope.
Identify systems using the i.MX SCU clock driver.
Compare deployed kernel source or changelog against the referenced stable commits.
Confirm distribution security notes for whether the fix was backported.
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-50559 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
5Source 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.
Oct 22, 2025, 13:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.