CVE-2025-38633
BaseFortify
Publication date: 2025-08-22
Last updated on: 2025-11-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves the Linux kernel's clock management system, specifically the pll1_d8 clock which is a parent clock for many others including those used by APB and AXI buses. The issue occurs because the pll1_d8 clock, enabled by the boot loader, could be disabled unintentionally when the system responds to a probe deferral (-EPROBE_DEFER) during reset controller requests. Disabling the CLK_DMA clock and its parents led to the pll1_d8 clock's enable count dropping to zero, causing it to be disabled and resulting in a system hang. The fix was to mark the pll1_d8 clock as critical to prevent it from being disabled.
How can this vulnerability impact me? :
This vulnerability can cause a system hang due to the unintended disabling of a critical clock (pll1_d8) in the Linux kernel. Since this clock is a parent to many others used by important buses (APB and AXI), its disablement can halt system operations, leading to potential downtime or system instability.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is resolved by marking the pll1_d8 clock as critical to prevent it from being disabled, which avoids system hangs. Immediate mitigation involves updating the Linux kernel to a version that includes this fix.