LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38654: pinctrl: canaan: k230: Fix order of DT parse and pinctrl register

In the Linux kernel, the following vulnerability has been resolved: pinctrl: canaan: k230: Fix order of DT parse and pinctrl register Move DT parse before pinctrl register. This ensures that device tree parsing is done before calling devm_pinctrl_register() to prevent using uninitialized pin resources.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a driver initialization bug: pin resources can be used before device-tree parsing initializes them. The public record does not state customer impact, CVSS severity, or active exploitation. Business urgency depends on whether deployed Linux systems include the affected Canaan K230 pinctrl code path.

Executive priority

Treat this as a targeted kernel maintenance item until stronger impact evidence appears. Escalate priority for embedded or appliance fleets using Canaan K230 Linux kernels; otherwise handle through normal patch governance and vendor advisory tracking.

Technical view

CVE-2025-38654 affects Linux kernel pinctrl code for Canaan K230. The fix moves device-tree parsing before devm_pinctrl_register(), preventing registration from seeing uninitialized pin resources. The source bundle does not describe a concrete crash, privilege impact, confidentiality impact, or exploit primitive.

Likely exposure

Exposure appears limited to Linux kernels carrying the affected Canaan K230 pinctrl implementation, especially systems whose builds and device trees exercise that driver. The provided affected-version data is not enough to map all vendor kernels or downstream backports reliably.

Exploitation context

The source bundle reports no CISA KEV listing and provides no evidence of public exploitation. The bug is in kernel driver initialization order, so realistic exposure likely depends on hardware, kernel configuration, and device-tree use rather than remote network reachability.

Researcher notes

Key unknowns are impact, reachability, and affected downstream kernel mappings. The public text only establishes an uninitialized pin-resource risk caused by registration before device-tree parsing. Do not infer active exploitation or broader Linux exposure without additional vendor evidence.

Mitigation direction

  • Check vendor kernel guidance for CVE-2025-38654 and affected downstream builds.
  • Update to a kernel release or vendor backport containing the referenced stable fixes.
  • Prioritize systems using Canaan K230-related kernel builds or device trees.
  • If patching is delayed, assess whether the K230 pinctrl driver is present and used.

Validation and detection

  • Inventory deployed kernel versions, source commits, and vendor backport status.
  • Confirm whether CONFIG_PINCTRL_CANAAN_K230 or equivalent driver support is enabled.
  • Review device trees for Canaan K230 pinctrl usage.
  • Verify the stable commit fix is present in source or vendor changelogs.
Prepared
Confidence
medium
Sources
5

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-38654 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
4Source 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
LinuxLinux545887eab6f6776a7477fe7e83860eab57138b03, 545887eab6f6776a7477fe7e83860eab57138b03, 545887eab6f6776a7477fe7e83860eab57138b03unaffected
LinuxLinux6.13, 0, 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.