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-98363 Overview
CVE-2026-98363 affects the Linux kernel's arm_scpi firmware driver. The scpi_dvfs_get_info() function trusted the opp_count value returned by the System Control Processor (SCP) firmware without validating an upper bound. The shared-memory reply buffer buf.opps[] holds at most MAX_DVFS_OPPS entries. A larger reported count causes the kernel to over-read the array and then allocate an incorrectly sized Operating Performance Point (OPP) table. The result is garbage OPP data or an out-of-bounds memory access. The missing upper bound dates back to the original SCPI Dynamic Voltage and Frequency Scaling (DVFS) support in the kernel.
Critical Impact
Untrusted SCP firmware input can trigger kernel out-of-bounds reads and memory corruption through the arm_scpi DVFS code path.
Affected Products
- Linux kernel versions containing the original SCPI DVFS support in drivers/firmware/arm_scpi.c
- Arm-based platforms using the System Control Processor Interface (SCPI) protocol
- Devices relying on scpi_dvfs_get_info() for DVFS table population
Discovery Timeline
- 2026-10-06 - CVE-2026-98363 published to the National Vulnerability Database (NVD)
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-98363
Vulnerability Analysis
The arm_scpi driver implements communication with Arm System Control Processor firmware over shared memory. The scpi_dvfs_get_info() function retrieves DVFS OPP tables from the SCP. It receives a reply structure containing an opp_count field followed by a fixed-size array buf.opps[] sized to MAX_DVFS_OPPS.
The existing validation rejected only a zero opp_count. Any larger value was accepted as-is. The driver then iterated over opp_count entries in the fixed-size reply buffer. This read past the end of buf.opps[], pulling adjacent shared-memory contents into the kernel. The driver subsequently allocated an OPP table sized from the attacker-influenced count, producing an incorrectly sized allocation populated with garbage data.
Root Cause
The root cause is missing upper-bound input validation [CWE-129] on a length field supplied by an external component. The SCPI DVFS code trusted that firmware-supplied counts matched the shared protocol constraints. No comparison against MAX_DVFS_OPPS guarded the loop or the subsequent allocation sizing.
Attack Vector
Exploitation requires the SCP firmware to return a crafted or corrupted opp_count greater than MAX_DVFS_OPPS. On systems where the SCP firmware is outside the kernel's trust boundary, or where firmware memory can be influenced, the response drives an out-of-bounds read in kernel context. The resulting OPP table contains uninitialized or adjacent memory data, which propagates through DVFS consumers. The fix rejects both zero and out-of-range counts in a single check and returns -EINVAL.
No public proof-of-concept code is referenced in the advisory. See the upstream commits linked under References for the exact patch logic.
Detection Methods for CVE-2026-98363
Indicators of Compromise
- Kernel log messages from the arm_scpi driver reporting failed DVFS initialization or -EINVAL returns from scpi_dvfs_get_info()
- Unexpected OPP table sizes or invalid frequency/voltage entries exposed through /sys/devices/system/cpu/cpufreq/
- Kernel Address Sanitizer (KASAN) reports flagging out-of-bounds reads inside drivers/firmware/arm_scpi.c
Detection Strategies
- Audit running kernel versions against the fixed commits (0130f9ad, 1aadbef6, 32471d84, 69ec03cd, 7daaa684, cc563a59, e9887eea, f17865332cc4) listed in the kernel git references
- Enable KASAN on test kernels for Arm platforms using SCPI to surface the out-of-bounds read during DVFS initialization
- Monitor dmesg at boot for scpi subsystem errors on affected hardware
Monitoring Recommendations
- Collect kernel boot logs centrally from Arm SoC fleets and alert on arm_scpi errors
- Track firmware image hashes on devices that expose the SCP firmware to update paths
- Correlate DVFS driver failures with firmware version changes to identify malformed replies
How to Mitigate CVE-2026-98363
Immediate Actions Required
- Update affected Linux kernels to a version containing the arm_scpi upper-bound check against MAX_DVFS_OPPS
- Inventory Arm platforms that enable CONFIG_ARM_SCPI_PROTOCOL and CONFIG_ARM_SCPI_CPUFREQ and prioritize patching
- Verify SCP firmware images against vendor-signed baselines to reduce the risk of malformed DVFS responses
Patch Information
The upstream fix adds a single check rejecting both zero and out-of-range opp_count values and returns -EINVAL. The fix is distributed across stable branches in the following commits: 0130f9ad, 1aadbef6, 32471d84, 69ec03cd, 7daaa684, cc563a59, e9887eea, and f17865332cc4.
Workarounds
- Disable the SCPI DVFS driver on platforms where it is not required by unsetting CONFIG_ARM_SCPI_PROTOCOL in the kernel configuration
- Restrict firmware update channels so that only signed, vendor-supplied SCP images can modify shared-memory DVFS responses
- Where feasible, isolate SCP firmware memory regions from mutable storage paths accessible to lower-privilege components
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

