CVE-2026-98362

Unknown

Last modified

CVE-2026-98362 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate dvfs_get_idx() may return an out-of-range index if the SCP firmware is buggy or returns a stale value. Only negative indexes were rejected, so a large index walked past info->opps and could treat garbage as a clock rate (KASAN OOB / wrong frequency to consumers).

Description

In the Linux kernel, the following vulnerability has been resolved: clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate dvfs_get_idx() may return an out-of-range index if the SCP firmware is buggy or returns a stale value. Only negative indexes were rejected, so a large index walked past info->opps and could treat garbage as a clock rate (KASAN OOB / wrong frequency to consumers). The missing upper bound dates back to the original SCPI clock driver. Treat indexes >= opp count as invalid and return 0, same as idx < 0.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 6e3b55823da8ef0d99621efb422cc29f50d7f280; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 7204095917aeaac89db7377c29a457351a19b076; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 56b7a9d89c67932bf11b71e3b6d17941fc24a393; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < a82b274697d0876b478594ca78ad1e6cb062467b; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < e1188332a9110cf3635fe286481ee38305b3c2b6; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 108c46e8dacc4a0e472a74f98171115d49cbc079; >= cd52c2a4b5c43631e429d06dce12e08b0cab477f, < 70f4b78d560e592cbf3325b162424737d032fc1d
LinuxLinux4.4

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98362?
In the Linux kernel, the following vulnerability has been resolved: clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate dvfs_get_idx() may return an out-of-range index if the SCP firmware is buggy or returns a stale value. Only negative indexes were rejected, so a large index walked past info->opps and could treat garbage as a clock rate (KASAN OOB / wrong frequency to consumers). The missing upper bound dates back to the original SCPI clock driver. Treat indexes >= opp count as invalid and return 0, same as idx < 0.
How severe is CVE-2026-98362?
Severity scoring for CVE-2026-98362 is pending analysis.
How do I fix CVE-2026-98362?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98362?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST