[CVE-2026-80609][MODERATE 7.0] qede: fix out-of-bounds check for cqe->len_list[] [ Upstream

[CVE-2026-80609][MODERATE 7.0] qede: fix out-of-bounds check for cqe->len_list[] [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80609
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: qede: fix out-of-bounds check for cqe->len_list[] [ Upstream
Commit: 6d203bdd227fca1787f8a80cf84b990936633c5a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6d203bdd227fca1787f8a80cf84b990936633c5a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80609
Analysis date: Fri, 28 Aug 2026 06:11:07 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
An out of bounds read in the qede TPA receive path occurs because cqe len_list is accessed before the index bounds check, allowing network influenced CQE processing to potentially crash the kernel or corrupt skb construction under qede TPA conditions.

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

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

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: MODERATE 7.0
Manual review required: YES

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

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

CVE-2026-80609	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';CWE-125;CWE-129;*CWE-20;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'An out of bounds read in the qede TPA receive path can occur because cqe len_list is read before the loop checks that the index is within ARRAY_SIZE. A remote sender may be able to influence the RX aggregation path by sending traffic that reaches a host using the qede driver with TPA enabled, although reliable triggering depends on NIC firmware behavior and CQE generation. For the CVSS the PR:N is used because no local account on the victim is required if the vulnerable network interface is reachable by the attacker. The issue is network reachable through received Ethernet traffic rather than through a local device interface. Impact is at least denial of service via kernel crash. In the paranoid interpretation, limited confidentiality or integrity impact is kept possible because an out of bounds value is consumed by later skb fragment handling, but the patch does not show an arbitrary write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-80609 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 896f1a2493b5 YES  NO NO unknown 	MAYBE	REMOTE WRITE OOB SIMPLEFIX NETWORK LINUS KPANIC MEMORY  KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6	-	-	checked

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2. The affected code is in the qede RX TPA receive path and can be reached by traffic arriving at a host using the qede driver.
* Memory corruption, weak/indirect corruption candidate: +1. The bug is an out-of-bounds read caused by evaluating `cqe->len_list[i]` before checking `i < ARRAY_SIZE`.
* Reliable kernel crash / strong DoS concern: +1. The out-of-bounds value is consumed as a fragment length in `qede_fill_frag_skb()`, so malformed or unexpected CQE state can plausibly crash or destabilize the receive path.
* Common networking packet-processing path: +1. This is in a network receive path, although hardware-specific.
* Hard or unreliable trigger / special conditions: -1. Triggering depends on qede hardware, TPA aggregation state, CQE contents, and firmware or NIC behavior.

Paranoid additional adjustment:

* Confidentiality impact plausible: +1. Limited OOB read from adjacent kernel/CQE memory is possible, although no user-visible disclosure path is shown.
* Integrity impact plausible: +1. A stale or adjacent value may be interpreted as a fragment length and affect skb construction.
* Corruption primitive highly constrained / no attacker-controlled payload: -1. The patch shows an over-indexed read, not an OOB write, arbitrary write, UAF reclaim, or controlled object replacement.

## 3. Reachability analysis

A remote sender may influence this path by sending network traffic to an interface handled by the qede driver with TPA enabled. No local account on the victim is required for the network-facing interpretation, so PR:N is reasonable for CVSS-style reporting when the interface is reachable. Practical triggering is still constrained by NIC firmware behavior and whether the CQE `len_list` can reach the unterminated condition. This is not a generic TCP/IP core bug and only affects systems using the relevant QLogic qede hardware and driver path.

## 4. Severity interpretation

This is more than an ordinary low-priority correctness issue because it is a network-reachable kernel out-of-bounds read in a receive driver path. It is not a strong Important-class case by itself because the patch does not show OOB write, UAF, type confusion, arbitrary write, or attacker-controlled reclaim. The realistic impact is DoS. The paranoid interpretation keeps limited C/I concern because the OOB value is consumed by skb fragment handling, but this remains a constrained primitive.

## 5. One-sentence report phrase

An out of bounds read in the qede TPA receive path occurs because cqe len_list is accessed before the index bounds check, allowing network influenced CQE processing to potentially crash the kernel or corrupt skb construction under qede TPA conditions.

## 6. Manual review recommendation

YES REQUIRES MANUAL CHECK
MANUAL CHECK REQUIRED. This is a network-reachable kernel memory-safety issue in an RX driver path, even though the demonstrated primitive is only a constrained OOB read and the likely practical impact is DoS.

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

Patch: qede: fix out-of-bounds check for cqe->len_list[] [ Upstream
Commit: 6d203bdd227fca1787f8a80cf84b990936633c5a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6d203bdd227fca1787f8a80cf84b990936633c5a

Changed files:
  drivers/net/ethernet/qlogic/qede/qede_fp.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=6d203bdd227fca1787f8a80cf84b990936633c5a

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

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

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:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 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: 4
  Paranoid ActionableScore: 5

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: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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