LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38655: pinctrl: canaan: k230: add NULL check in DT parse

In the Linux kernel, the following vulnerability has been resolved: pinctrl: canaan: k230: add NULL check in DT parse Add a NULL check for the return value of of_get_property() when retrieving the "pinmux" property in the group parser. This avoids a potential NULL pointer dereference if the property is missing from the device tree node. Also fix a typo ("sintenel") in the device ID match table comment, correcting it to "sentinel".

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 reliability flaw in the Canaan K230 pin control driver. If a required device-tree “pinmux” property is missing, the kernel may dereference NULL and crash. The sources do not show data theft, privilege escalation, or remote exploitation.

Executive priority

Treat as routine patch management unless the organization ships or operates Canaan K230-based Linux devices. Prioritize higher if device crashes affect production availability, safety, or customer appliances.

Technical view

The K230 pinctrl group parser called of_get_property() for “pinmux” without checking for NULL. A missing property in a device tree node could trigger a NULL pointer dereference. The referenced stable commits add the NULL check and correct a comment typo.

Likely exposure

Exposure appears limited to Linux systems using the Canaan K230 pinctrl driver with affected kernel code and a missing or malformed relevant device-tree property. General-purpose Linux servers are unlikely to be exposed unless they include this hardware path.

Exploitation context

CISA KEV status is false in the bundle, and no cited source reports active exploitation. The described trigger depends on device-tree content, suggesting a local configuration or platform-specific reliability issue rather than a broadly reachable attack surface.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit report, or detailed impact statement is provided. The fix is narrow and source-level: add a NULL check around the “pinmux” property lookup in the K230 pinctrl parser.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Track Linux distribution advisories for backported kernel packages.
  • For embedded builds, verify the K230 pinctrl patch is included.
  • Review device-tree nodes for required “pinmux” properties.
  • If no package exists, follow vendor guidance for safe backporting.

Validation and detection

  • Check running kernel version and vendor patch level.
  • Confirm whether the Canaan K230 pinctrl driver is built or loaded.
  • Inspect platform device-tree sources for K230 pinctrl nodes.
  • Verify the relevant stable commit is present in kernel source.
  • Run regression testing on affected embedded hardware after updating.
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-38655 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.