# CVE-2026-98363: firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS

> A missing bounds check in the Linux kernel SCPI driver allows out-of-bounds reads and potential memory corruption via malicious firmware responses.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106212, BELL-CVE-2026-98363, DEBIAN-CVE-2026-98363, GHSA-33vh-pc87-q32x, UBUNTU-CVE-2026-98363

## What is CVE-2026-98363?

CVE-2026-98363 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS

scpi_dvfs_get_info() already rejected a zero opp_count, but still trusted
any larger value from the SCP firmware. The shared-memory reply only holds
MAX_DVFS_OPPS entries in buf.opps[]; a bigger count over-reads that array
and then sizes the allocated OPP table incorrectly (garbage OPPs / OOB).
The missing upper bound dates back to the original SCPI DVFS support.

Reject zero and out-of-range counts in one check and return -EINVAL.

## Which versions are affected by CVE-2026-98363?


## How do I fix CVE-2026-98363?

Apply the vendor's patch.

## Is CVE-2026-98363 being exploited?

There is no known exploitation of CVE-2026-98363 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98363 and fix it if it is affected.

What it is: CVE-2026-98363 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98363 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98363/ (Markdown: https://insights.sbomify.com/CVE-2026-98363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98363
- OSV: https://osv.dev/vulnerability/CVE-2026-98363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98363/
Summaries are generated and may contain mistakes; the official description above is the record.