CVE-2026-98362: Linux kernel · clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e1188332a9110cf3635fe286481ee38305b3c2b6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e1188332a9110cf3635fe286481ee38305b3c2b6, a82b274697d0876b478594ca78ad1e6cb062467b, 7204095917aeaac89db7377c29a457351a19b076 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits. Users should update to a Linux kernel version that includes these fixes. Since this is a kernel-level vulnerability, applying the official patches or upgrading the kernel is the recommended remediation.
Description
A vulnerability in the Linux kernel's SCPI clock driver allows an out-of-range DVFS index to be used due to missing upper bound checks. This can cause out-of-bounds access leading to incorrect clock rates being reported to consumers. The issue has been fixed by adding proper upper bound validation to reject invalid indexes.
References
- git.kernel.org/stable/c/6e3b55823da8ef0d99621efb422cc29f50d7f280 (opens in a new tab)
- git.kernel.org/stable/c/7204095917aeaac89db7377c29a457351a19b076 (opens in a new tab)
- git.kernel.org/stable/c/0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a (opens in a new tab)
- git.kernel.org/stable/c/56b7a9d89c67932bf11b71e3b6d17941fc24a393 (opens in a new tab)
- git.kernel.org/stable/c/a82b274697d0876b478594ca78ad1e6cb062467b (opens in a new tab)
- git.kernel.org/stable/c/e1188332a9110cf3635fe286481ee38305b3c2b6 (opens in a new tab)
- git.kernel.org/stable/c/108c46e8dacc4a0e472a74f98171115d49cbc079 (opens in a new tab)
- git.kernel.org/stable/c/70f4b78d560e592cbf3325b162424737d032fc1d (opens in a new tab)