# CVE-2026-90314: remoteproc: fix OOB read via signed offset in rsc_table_for_each_entry()

> A signed integer overflow in the Linux kernel remoteproc driver allows out-of-bounds reads via crafted firmware offsets, potentially leading to information disclosure or crashes.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102039, BELL-CVE-2026-90314, DEBIAN-CVE-2026-90314, GHSA-vjc5-x57x-7c9h, UBUNTU-CVE-2026-90314

## What is CVE-2026-90314?

CVE-2026-90314 is a vulnerability in Linux, published on 17 Sep 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:

remoteproc: fix OOB read via signed offset in rsc_table_for_each_entry()

table->offset[i] is a u32 from firmware, but was stored into a signed
int.  A crafted offset like 0xFFFFFFF0 becomes -16, placing hdr 16 bytes
before the table buffer.  The subsequent avail check was bypassed
because the negative int was promoted to a large size_t in the
expression "table_sz - offset - sizeof(*hdr)", yielding a large positive
avail and letting the out-of-bounds hdr->type read proceed undetected.

Store the offset as u32 and validate it with unsigned comparisons before
any pointer arithmetic.

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


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

Apply the vendor's patch.

## Is CVE-2026-90314 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90314 is a vulnerability in Linux, published on 17 Sep 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-90314 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-90314/ (Markdown: https://insights.sbomify.com/CVE-2026-90314/index.md)
```

## Sources

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

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