Skip to main content
Vulnerability Database/CVE-2026-98362

CVE-2026-98362: Linux Kernel SCPI Clock Privilege Escalation

CVE-2026-98362 is a privilege escalation vulnerability in the Linux kernel SCPI clock driver that allows out-of-bounds memory access through improper index validation. This article covers technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98362 Overview

CVE-2026-98362 is a Linux kernel vulnerability in the System Control and Power Interface (SCPI) clock driver. The flaw resides in the scpi_dvfs_recalc_rate() function within the Dynamic Voltage and Frequency Scaling (DVFS) subsystem. The function failed to validate the upper bound of indexes returned by dvfs_get_idx(), rejecting only negative values. A large index returned by buggy or stale SCP firmware walked past the info->opps array, triggering a Kernel Address Sanitizer (KASAN) out-of-bounds read and potentially delivering garbage data as a clock frequency to consumers. The missing bound check dates back to the original SCPI clock driver implementation.

Critical Impact

An out-of-bounds read in kernel memory can leak kernel data to clock consumers and produce incorrect frequency values, potentially destabilizing systems that rely on SCPI-managed DVFS.

Affected Products

  • Linux kernel versions containing the SCPI clock driver (drivers/clk/clk-scpi.c)
  • ARM-based platforms using System Control Processor (SCP) firmware with SCPI protocol
  • Systems using DVFS clock operations through the SCPI interface

Discovery Timeline

  • 2026-10-06 - CVE-2026-98362 published to the National Vulnerability Database (NVD)
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-98362

Vulnerability Analysis

The vulnerability is an out-of-bounds read in the SCPI clock driver's DVFS rate recalculation path. When scpi_dvfs_recalc_rate() queries the current operating performance point index via dvfs_get_idx(), it previously validated only that the returned index was non-negative. No upper bound check against the operating performance points (OPP) count was performed.

If the SCP firmware returned a stale or erroneous index greater than or equal to the number of defined OPPs, the driver indexed past the end of the info->opps array. The resulting read returned uninitialized or adjacent kernel memory and treated it as a valid clock rate. Downstream consumers of the clock framework then received an incorrect frequency value, with potential impact on system stability or hardware state.

Root Cause

The root cause is missing input validation on data returned from an external firmware component. The original SCPI clock driver implementation trusted the index returned by dvfs_get_idx() to fall within the configured OPP table bounds. This assumption classifies the issue as an Out-of-Bounds Read [CWE-125] arising from improper validation of an array index [CWE-129].

Attack Vector

Exploitation requires the SCP firmware to return an out-of-range DVFS index. This condition is reachable through buggy firmware, firmware state corruption, or stale cached values during clock recalculation. The flaw is not remotely exploitable over a network and is not associated with any known public exploit or in-the-wild activity. The Exploit Prediction Scoring System (EPSS) rates the probability of exploitation at 0.172%.

The patch treats indexes >= opp count as invalid and returns 0, matching the existing behavior for negative indexes. See the upstream fix in the kernel.org commit for the exact code change.

Detection Methods for CVE-2026-98362

Indicators of Compromise

  • KASAN splat reports referencing scpi_dvfs_recalc_rate or info->opps in kernel logs
  • Unexpected or implausible clock frequency values reported by consumers of SCPI-managed clocks
  • Kernel oops or warnings originating from drivers/clk/clk-scpi.c during DVFS transitions

Detection Strategies

  • Review dmesg and persistent kernel logs for KASAN out-of-bounds read reports in the SCPI clock driver call stack
  • Audit running kernel versions against the fixed commits listed in the upstream references
  • Correlate SCP firmware version information with kernel versions to identify systems running vulnerable combinations

Monitoring Recommendations

  • Centralize kernel log collection from ARM platforms and alert on KASAN or BUG reports referencing clock subsystem functions
  • Track package and kernel versions across the fleet to confirm patch deployment
  • Monitor platform telemetry for anomalous CPU frequency transitions that may indicate incorrect rate reporting

How to Mitigate CVE-2026-98362

Immediate Actions Required

  • Apply the upstream Linux kernel patch that adds the upper bound check in scpi_dvfs_recalc_rate()
  • Update to a stable kernel release that incorporates the fix for the affected branch in use
  • Verify SCP firmware is current and known-good to reduce the likelihood of invalid DVFS indexes being returned

Patch Information

The fix was committed across multiple stable kernel branches. Relevant upstream commits include commit 0f89e2ac0e94, commit 108c46e8dacc, commit 56b7a9d89c67, commit 6e3b55823da8, commit 70f4b78d560e, commit 7204095917ae, commit a82b274697d0, and commit e1188332a911. The change treats indexes greater than or equal to the OPP count as invalid, returning 0 as scpi_dvfs_recalc_rate() already does for negative indexes.

Workarounds

  • No supported runtime workaround exists in the kernel; apply the patch
  • If patching is temporarily deferred, disable or avoid use of the SCPI clock driver on affected platforms where feasible
  • Validate SCP firmware behavior in test environments to detect out-of-range DVFS index responses before production deployment

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.