# CVE-2026-74451: drm/panthor: validate firmware interface structure sizes

> A missing size validation in the Panthor GPU driver allows out-of-bounds memory access, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74451, DEBIAN-CVE-2026-74451, GHSA-hm75-jr86-gwf9, UBUNTU-CVE-2026-74451

## What is CVE-2026-74451?

CVE-2026-74451 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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:

drm/panthor: validate firmware interface structure sizes

iface_fw_to_cpu_addr() only checks that the firmware-provided MCU virtual
address points inside the shared section. The returned pointer is later
used as a full firmware interface structure, so accepting an address near
the end of the shared section can still lead to out-of-bounds accesses.

Pass the expected object size to iface_fw_to_cpu_addr() and reject ranges
that do not fit entirely in the shared section.

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


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

Apply the vendor's patch.

## Is CVE-2026-74451 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74451 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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-74451 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-74451/ (Markdown: https://insights.sbomify.com/CVE-2026-74451/index.md)
```

## Sources

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

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