Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Local vector confirmed by driver-level access; PR:L because any local user can trigger cpufreq scaling; A:H for kernel panic; no confidentiality or integrity impact described.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
5DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved:
clk: spacemit: ccu_mix: fix inverted condition in ccu_mix_trigger_fc()
Fix inverted condition that skips frequency change trigger, causing kernel panics during cpufreq scaling.
AnalysisAI
Kernel panic in the SpaceMIT clock controller driver (clk-spacemit-ccu) can be triggered during CPU frequency scaling on systems running SpaceMIT RISC-V hardware. The root cause is an inverted boolean condition in ccu_mix_trigger_fc() that causes the frequency change trigger to be skipped at the wrong time and fired at the wrong time, crashing the kernel under normal cpufreq governor activity. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires: (1) a system physically or virtually running SpaceMIT K1 RISC-V hardware with the SpaceMIT CCU mix clock driver loaded; (2) a dynamic CPU frequency governor active (schedutil, ondemand, conservative, or interactive) so that cpufreq scaling is triggered; (3) local access with at minimum standard user privileges sufficient to execute workloads that cause frequency transitions (PR:L per CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) reflects a local denial-of-service: a low-privilege local user on an affected system can trigger a kernel panic simply by inducing cpufreq scaling, which can occur under normal system operation without intentional attack. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A local user on a SpaceMIT K1 development board running an unpatched kernel triggers a workload spike (e.g., a CPU-intensive compile job), causing the `schedutil` cpufreq governor to request a frequency change. The kernel calls `ccu_mix_trigger_fc()`, the inverted condition causes the hardware trigger to be skipped, the clock state becomes inconsistent, and the kernel panics - crashing the system. … |
| Remediation | Update to a patched Linux kernel version: 6.18.33, 7.0.10, or 7.1 (or later). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-38887
GHSA-399v-vw49-mfxj