LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38583: clk: xilinx: vcu: unregister pll_post only if registered correctly

In the Linux kernel, the following vulnerability has been resolved: clk: xilinx: vcu: unregister pll_post only if registered correctly If registration of pll_post is failed, it will be set to NULL or ERR, unregistering same will fail with following call trace: Unable to handle kernel NULL pointer dereference at virtual address 008 pc : clk_hw_unregister+0xc/0x20 lr : clk_hw_unregister_fixed_factor+0x18/0x30 sp : ffff800011923850 ... Call trace: clk_hw_unregister+0xc/0x20 clk_hw_unregister_fixed_factor+0x18/0x30 xvcu_unregister_clock_provider+0xcc/0xf4 [xlnx_vcu] xvcu_probe+0x2bc/0x53c [xlnx_vcu]

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2025-38583 is a Linux kernel reliability flaw in the Xilinx VCU clock driver. If one clock registration fails, cleanup can incorrectly unregister an invalid pointer and hit a kernel NULL pointer dereference. Evidence points to a narrow, hardware-specific crash condition, not broad remote compromise.

Executive priority

Treat this as a targeted maintenance issue for Xilinx VCU-based Linux systems. It does not currently justify emergency response across all Linux assets, but affected embedded or appliance platforms should be patched through normal kernel update channels.

Technical view

The xlnx_vcu driver may call clk_hw_unregister_fixed_factor on pll_post after failed registration, where pll_post can be NULL or an ERR pointer. The reported trace reaches clk_hw_unregister during xvcu_probe cleanup. Stable kernel commits correct the unregister condition across supported branches.

Likely exposure

Likely limited to Linux systems using the Xilinx VCU driver or kernels built for platforms where that driver can probe. General Linux servers without this hardware path are unlikely to be exposed based on the provided sources.

Exploitation context

No active exploitation is evidenced. The CVE is not listed as KEV in the provided bundle, and no source describes public exploitation. The known impact is a kernel NULL pointer dereference during a driver failure path.

Researcher notes

The public record lacks CVSS, CWE mapping, and a detailed threat model. Analysis should focus on driver probe error handling, affected kernel branch mapping, and whether local configuration or hardware state can trigger pll_post registration failure.

Mitigation direction

  • Apply vendor or distribution kernel updates that include the referenced stable fixes.
  • Prioritize Xilinx VCU embedded or appliance fleets over general-purpose Linux servers.
  • Check Debian LTS guidance if running Debian kernels covered by the advisory.
  • If no packaged fix exists, follow kernel or distribution vendor guidance.

Validation and detection

  • Inventory kernels and devices using the xlnx_vcu or Xilinx VCU driver.
  • Compare deployed kernel versions with vendor fixed package or stable commit coverage.
  • Review boot and kernel logs for xvcu_probe or clk_hw_unregister NULL dereference traces.
  • Confirm patched systems no longer use vulnerable driver cleanup logic.
Prepared
Confidence
medium
Sources
10

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-38583 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
9Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849fe, 4472e1849db7f719bbf625890096e0269b5849feunaffected
LinuxLinux5.12, 0, 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.