LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38631: clk: imx95-blk-ctl: Fix synchronous abort

In the Linux kernel, the following vulnerability has been resolved: clk: imx95-blk-ctl: Fix synchronous abort When enabling runtime PM for clock suppliers that also belong to a power domain, the following crash is thrown: error: synchronous external abort: 0000000096000010 [#1] PREEMPT SMP Workqueue: events_unbound deferred_probe_work_func pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : clk_mux_get_parent+0x60/0x90 lr : clk_core_reparent_orphans_nolock+0x58/0xd8 Call trace: clk_mux_get_parent+0x60/0x90 clk_core_reparent_orphans_nolock+0x58/0xd8 of_clk_add_hw_provider.part.0+0x90/0x100 of_clk_add_hw_provider+0x1c/0x38 imx95_bc_probe+0x2e0/0x3f0 platform_probe+0x70/0xd8 Enabling runtime PM without explicitly resuming the device caused the power domain cut off after clk_register() is called. As a result, a crash happens when the clock hardware provider is added and attempts to access the BLK_CTL register. Fix this by using devm_pm_runtime_enable() instead of pm_runtime_enable() and getting rid of the pm_runtime_disable() in the cleanup path.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-38631 is a Linux kernel crash bug in the i.MX95 block-control clock driver. A power-management sequencing issue can cut power before the clock provider accesses hardware registers, causing a synchronous abort. The main business impact is availability risk on affected systems, especially embedded or appliance-like Linux deployments using this driver path.

Executive priority

Handle in normal kernel maintenance unless affected i.MX95-based systems are business-critical or showing crashes. There is no source-backed evidence of active exploitation, but unpatched devices may suffer stability failures that disrupt operations.

Technical view

The bug is in clk: imx95-blk-ctl. Runtime PM was enabled without explicitly resuming a device that also belonged to a power domain. After clk_register(), the power domain could turn off, and of_clk_add_hw_provider() could later access the BLK_CTL register, triggering a synchronous external abort in clk_mux_get_parent().

Likely exposure

Exposure appears limited to Linux kernels using the i.MX95 BLK_CTL clock/power-domain path. The source lists Linux as affected and references version markers including 6.10, 6.12.42, 6.15.10, 6.16.1, and 6.17. Downstream distribution and device-vendor status needs separate confirmation.

Exploitation context

The provided sources do not show active exploitation, KEV listing, remote attackability, or a public exploit. The evidence describes a kernel crash during device probing and clock provider registration, so treat this primarily as a reliability and availability issue unless vendor advisories add more context.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. The root cause is runtime PM lifecycle handling around a power-domain-backed clock supplier. The fix replaces pm_runtime_enable() cleanup handling with devm_pm_runtime_enable(), preventing the premature power-domain cutoff described in the record.

Mitigation direction

  • Apply a kernel build containing the referenced stable fixes.
  • Check Linux distribution or device-vendor advisories for backported patches.
  • Prioritize systems using i.MX95 or the imx95-blk-ctl driver.
  • Avoid direct deployment changes until vendor kernel compatibility is confirmed.
  • Track logs for synchronous external aborts during probe or boot.

Validation and detection

  • Inventory kernel versions and enabled i.MX95 BLK_CTL support.
  • Map deployed kernels against vendor-fixed builds or stable commits.
  • Review boot and probe logs for clk_mux_get_parent abort traces.
  • Confirm patched driver uses devm_pm_runtime_enable() behavior.
  • Regression-test affected hardware boot and runtime power-management paths.
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-2025-38631 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
LinuxLinux5224b189462ff70df328f173b71acfd925092c3c, 5224b189462ff70df328f173b71acfd925092c3c, 5224b189462ff70df328f173b71acfd925092c3c, 5224b189462ff70df328f173b71acfd925092c3cunaffected
LinuxLinux6.10, 0, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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