[CVE-2026-80577][LOW] drm/panthor: skip zero-sized firmware sections

[CVE-2026-80577][LOW] drm/panthor: skip zero-sized firmware sections

[AL-KERNEL]

CVE: CVE-2026-80577
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/panthor: skip zero-sized firmware sections
Commit: f0f3c3922db981031733a25c51e1f37cf9b9e251
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f0f3c3922db981031733a25c51e1f37cf9b9e251
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80577
Analysis date: Wed, 26 Aug 2026 13:49:03 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL pointer dereference in the drm panthor firmware path can occur when a zero sized firmware section is added with section mem left as NULL and later reload or unplug paths dereference it, causing a local device specific denial of service.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80577 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80577

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-80577	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;*CWE-20;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A NULL pointer dereference in the drm panthor firmware path can occur because a zero sized firmware section may be accepted into the firmware section list with section mem left as NULL. Later reload or unplug paths iterate over all firmware sections and may dereference this NULL field, causing a kernel crash. For the CVSS the PR:L is used only in the paranoid case because some deployments expose GPU render nodes to local unprivileged users and such users may be able to influence GPU reset or recovery behavior. The issue is not network reachable and requires a local system context or device management path. Impact is denial of service via kernel crash, with no concrete evidence of information disclosure or privilege escalation from this patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-80577 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	NULLPTR SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit states that reload and unplug paths may dereference section->mem when it is NULL.
* Firmware-mediated external influence: +1. The problematic object is derived from firmware section metadata, but this is not a normal remote input path.
* Requires admin/root/CAP_* in typical deployments: -2. Firmware replacement, device reload, driver management, and unplug paths are normally admin or system controlled.
* Rare AND difficult-to-reach subsystem/configuration: -1. This is specific to Panthor GPU firmware handling and requires a zero-sized firmware section plus later reload or unplug behavior.
* Conservative total is clamped to 0.

Paranoid signals:

* Firmware-mediated external influence: +1.
* Local unprivileged trigger: +1 only as a paranoid interpretation if local unprivileged GPU users can trigger recovery or reset paths through render node activity.
* Reliable kernel crash / strong DoS: +1.
* Rare AND difficult-to-reach subsystem/configuration: -1.
* Paranoid total: 2.

Not awarded:

* No generic memory corruption. The demonstrated primitive is NULL pointer dereference, not UAF, double free, OOB write, refcount misuse, or type confusion.
* No privilege escalation plausible. There is no reclaim, overwrite, callback control, or attacker-controlled object replacement.
* No confidentiality or integrity impact. The patch context supports crash only.

## 3. Reachability analysis

Typical triggering requires a Panthor device and firmware containing a valid zero-sized section. The NULL dereference is reached later through firmware reload or unplug paths. In normal deployments, firmware contents and device-management paths are controlled by root or by the system, so the conservative interpretation treats this as a privileged local DoS.

A paranoid local-user interpretation is possible only if unprivileged access to the GPU render node can reliably force GPU recovery, reset, or firmware reload after such a section has been loaded. That still does not make the issue network reachable and does not establish memory corruption beyond a NULL dereference.

Call-site confidence: medium. The commit message explicitly identifies reload and unplug dereference paths, but the supplied diff only shows the early return in panthor_fw_load_section_entry().

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel DoS issue. The realistic impact is a kernel crash through NULL pointer dereference in a device-specific firmware path. Theoretical escalation is not supported by the patch because there is no UAF, stale pointer reuse, writable corruption sink, or object confusion.

## 5. One-sentence report phrase

A NULL pointer dereference in the drm panthor firmware path can occur when a zero sized firmware section is added with section mem left as NULL and later reload or unplug paths dereference it, causing a local device specific denial of service.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can likely be auto-closed for most triage queues because the supported impact is DoS only, the path is device-specific, and exploitation normally depends on privileged firmware or device-management conditions.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: drm/panthor: skip zero-sized firmware sections
Commit: f0f3c3922db981031733a25c51e1f37cf9b9e251
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f0f3c3922db981031733a25c51e1f37cf9b9e251

Commit description:

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.

Fixes: 2718d91 ("drm/panthor: Add the FW logical block")
Cc: stable@vger.kernel.org
Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Steven Price <steven.price@arm.com>
Link: https://patch.msgid.link/20260724172621.63046-1-osama.abdelkader@gmail.com
Signed-off-by: Steven Price <steven.price@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/gpu/drm/panthor/panthor_fw.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f0f3c3922db981031733a25c51e1f37cf9b9e251

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80577 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80577

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).