LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53572: clk: imx: scu: use _safe list iterator to avoid a use after free

In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it dereferences a freed variable to get the next item on the loop.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53572 is a Linux kernel memory-safety bug in the i.MX SCU clock driver. The code freed a clock object while iterating and could then dereference freed memory. Business impact is not scored in the sources, so urgency depends on whether affected Linux kernels and i.MX platforms exist in your fleet.

Executive priority

Set priority after confirming affected i.MX Linux assets. For organizations with embedded Linux products or appliances, schedule remediation through normal kernel maintenance unless vendor guidance raises severity. For fleets without i.MX SCU exposure, business urgency appears limited from the available evidence.

Technical view

The fix changes a list iteration in clk: imx: scu to a safe iterator because the loop frees clk entries. Without list_for_each_entry_safe(), the next loop access can dereference a freed variable. Sources identify Linux kernel affected versions and stable commit references, but provide no CVSS, CWE, or exploitability assessment.

Likely exposure

Most relevant exposure is Linux systems using affected kernel versions with the i.MX SCU clock driver. This likely affects embedded or appliance-style ARM deployments more than general servers, but the provided sources do not define exact configurations or distributions.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or impact scoring. Treat this as a kernel use-after-free requiring patch tracking, not as confirmed exploited-in-the-wild activity.

Researcher notes

The record is sparse: no CVSS, CWE, patch impact notes, or exploitability statement are provided. Analysis should focus on code reachability in clk-imx-scu deployments, fixed commit presence, and downstream vendor backports rather than assuming broad Linux exposure.

Mitigation direction

  • Apply Linux stable or vendor kernel updates containing the referenced fixes.
  • If using vendor BSP kernels, request the corresponding backport from the device or silicon vendor.
  • Prioritize i.MX systems using the SCU clock driver.
  • Monitor CVE and vendor advisories for severity or mitigation updates.

Validation and detection

  • Inventory Linux kernel versions across embedded, appliance, and ARM fleets.
  • Identify systems using NXP i.MX platforms or SCU clock support.
  • Check whether kernel source or packages include the referenced stable fixes.
  • Confirm vendor firmware or BSP releases document a backport for this CVE.
Prepared
Confidence
medium
Sources
7

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-53572 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
6Source 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
LinuxLinux77d8f3068c63ee0983f0b5ba3207d3f7cce11be4, 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4, 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4, 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4, 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4unaffected
LinuxLinux5.11, 0, 5.15.121, 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.