Menu

Star on GitHub · 3.2k

CVE-2026-80577

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 r…

Published Aug 26, 2026EPSS 0.21%

Overview

CVE-2026-80577 is a known-severity vulnerability. It was published on August 26, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80577?

CVE-2026-80577 is a known-severity vulnerability. It was published on August 26, 2026.

How severe is CVE-2026-80577?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80577?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80577?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80577 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.