# CVE-2026-80577: drm/panthor: skip zero-sized firmware sections

> A NULL pointer dereference in the Linux kernel Panthor GPU driver allows local attackers to cause a system crash by triggering specific firmware reload paths.

- **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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BELL-CVE-2026-80577, DEBIAN-CVE-2026-80577, UBUNTU-CVE-2026-80577

## What is CVE-2026-80577?

CVE-2026-80577 is a vulnerability in Linux, published on 26 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: skip zero-sized firmware sections

panthor_fw_load_section_entry() skips BO creation when the firmware section
VA range is empty. If such a section is added to the firmware section list,
section->mem is left as NULL.

Later reload and unplug paths iterate over all firmware sections and
dereference section->mem, which can lead to a NULL pointer dereference.

Zero-sized firmware sections are valid, so accept them as no-op entries but
skip adding them to the section list.

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


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

Apply the vendor's patch.

## Is CVE-2026-80577 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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