LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38635: clk: davinci: Add NULL check in davinci_lpsc_clk_register()

In the Linux kernel, the following vulnerability has been resolved: clk: davinci: Add NULL check in davinci_lpsc_clk_register() devm_kasprintf() returns NULL when memory allocation fails. Currently, davinci_lpsc_clk_register() does not check for this case, which results in a NULL pointer dereference. Add NULL check after devm_kasprintf() to prevent this issue and ensuring no resources are left allocated.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a reliability bug: under memory allocation failure, a DaVinci clock driver path can dereference a NULL pointer. The likely business impact is system instability or crash on affected kernels, especially embedded Linux systems using this driver. The source bundle does not show remote exploitation, privilege escalation, or active exploitation.

Executive priority

Treat as routine patch management unless affected systems support critical operations. Raise priority for embedded or operational technology devices where a kernel crash causes service disruption or field maintenance cost.

Technical view

davinci_lpsc_clk_register() used devm_kasprintf() without checking for NULL. If allocation failed, later use could trigger a NULL pointer dereference. Kernel stable commits add the missing NULL check and cleanup handling. No CVSS, CWE, or detailed attack vector is provided in the bundle.

Likely exposure

Exposure appears limited to Linux kernels including the DaVinci LPSC clock code and running affected kernel versions or downstream builds. Organizations with embedded Linux, ARM SoC, or vendor kernels should verify applicability with their kernel supplier.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The condition depends on allocation failure in a kernel driver path; practical exploitability beyond denial of service is not established by the sources.

Researcher notes

Evidence is sparse: no CVSS, CWE, reproducer, or attack preconditions are supplied. Analysis should stay close to the kernel commit text. Validate exposure by code presence, configuration, and vendor backports rather than version strings alone.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Use distribution advisories, including Debian LTS guidance, for package-specific remediation.
  • Check embedded vendor BSPs for backported kernel fixes.
  • Prioritize systems where kernel crashes affect safety or availability.

Validation and detection

  • Inventory kernel versions and downstream vendor kernel branches.
  • Confirm whether DaVinci clock driver code is built or deployed.
  • Map deployed kernels against the referenced stable commits.
  • Review vendor advisories for fixed package versions.
  • Monitor crash logs for NULL pointer dereferences in DaVinci clock code.
Prepared
Confidence
medium
Sources
12

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-38635 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
1ADP providers
12Source 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.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277, c6ed4d734bc7f731709dab0ffd69eed499dd5277unaffected
LinuxLinux4.17, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 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.