LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54221: clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe

In the Linux kernel, the following vulnerability has been resolved: clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe In function probe(), it returns directly without unregistered hws when error occurs. Fix this by adding 'goto unregister_hws;' on line 295 and line 310. Use devm_kzalloc() instead of kzalloc() to automatically free the memory using devm_kfree() when error occurs. Replace of_iomap() with devm_of_iomap() to automatically handle the unused ioremap region and delete 'iounmap(anatop_base);' in unregister_hws.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel resource-cleanup flaw in the i.MX93 clock driver. When driver initialization fails, memory and mapped resources may not be released. The sources do not show remote code execution, privilege escalation, public exploitation, or a CVSS score.

Executive priority

Treat as routine kernel maintenance unless i.MX93-based devices show stability issues. It does not justify emergency response from the provided evidence, but embedded Linux owners should include it in regular patch cycles.

Technical view

The flaw is in imx93_clocks_probe error handling. Some failure paths returned without unregistering hardware clocks, and allocation/mapping cleanup was incomplete. Stable fixes add unwind handling and devm-managed allocation/mapping.

Likely exposure

Likely limited to Linux systems using affected kernels with the i.MX93 clock driver built and exercised. General Linux servers without this hardware-specific driver path are unlikely to be exposed based on the provided sources.

Exploitation context

No active exploitation is reported in the supplied sources, and the CVE is not marked KEV. The described impact is resource leakage during probe failure, suggesting availability or reliability concern rather than direct compromise evidence.

Researcher notes

The affected-version data is incomplete and partly commit-oriented. The strongest evidence is the kernel stable patch set describing missing unwind paths and managed resource cleanup. No CWE, CVSS, exploitability detail, or product-specific advisory is provided.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize i.MX93-based systems and embedded fleets.
  • Avoid assuming fixed status from version numbers alone.
  • Track vendor kernel branches that carry custom clock drivers.

Validation and detection

  • Inventory systems running affected Linux kernel branches.
  • Confirm whether the i.MX93 clock driver is present and enabled.
  • Map deployed kernels to the listed stable commits or distro patches.
  • Review boot and driver initialization logs for probe failures.
  • Confirm vendor advisories for exact fixed package versions.
Prepared
Confidence
medium
Sources
6

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-2023-54221 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
5Source 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
LinuxLinux24defbe194b650218680fcd9dec8cd103537b531, 24defbe194b650218680fcd9dec8cd103537b531, 24defbe194b650218680fcd9dec8cd103537b531, 24defbe194b650218680fcd9dec8cd103537b531unaffected
LinuxLinux5.18, 0, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.