[CVE-2026-72339][IMPORTANT] qede: fix off-by-one in BD ring consumption on build_skb failure [ Upstream

[CVE-2026-72339][IMPORTANT] qede: fix off-by-one in BD ring consumption on build_skb failure [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72339
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: qede: fix off-by-one in BD ring consumption on build_skb failure [ Upstream
Commit: ecc05d4b20220a09c9c69584fc46ca55248a374a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ecc05d4b20220a09c9c69584fc46ca55248a374a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72339
Analysis date: Sat, 15 Aug 2026 07:28:04 -0400
ActionableScore: 7
ActionableScore lower bound: 6
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A qede RX error path can consume one extra BD after qede_build_skb() fails under memory pressure, desynchronizing the RX ring and potentially causing DMA page refcount corruption, SLUB freelist corruption, and remote kernel DoS on affected NICs.

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

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

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: IMPORTANT
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-72339	IMPORTANT	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';CWE-193;*CWE-416;CWE-119;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '8.1';DESCR 'A memory corruption risk exists in the qede RX path because qede_rx_build_skb() and qede_tpa_rx_build_skb() can continue BD ring processing after qede_build_skb() returns NULL under memory pressure. This consumes one extra BD and can desynchronize the RX BD ring, corrupt DMA page reference counts, and lead to SLUB freelist corruption. A remote sender can potentially reach this path by delivering traffic to a host using a qede interface, but reliable triggering depends on memory pressure and RX ring state. For the CVSS the PR:N is used because no local account is needed when the vulnerable interface is reachable over the network. Impact is at least denial of service via kernel crash and in the paranoid case may include confidentiality or integrity impact because the patch context explicitly mentions DMA page reference count corruption and SLUB freelist corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7)	YES	REMOTE OOB DANGER NULLPTR SIMPLEFIX NETWORK SKB DMAorINTERRUPT KPANIC MEMORY  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS	NO	NO	checked

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

ActionableScore=7
ActionableScoreLower=6

## 1. ActionableScore

* Conservative score: 6
* Paranoid score: 7
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2. The bug is in the qede RX path, so crafted or high-volume network traffic can reach the affected code on systems using a qede NIC.
* Weak LPE concern: +1. The commit explicitly mentions DMA page reference count corruption and SLUB freelist corruption, but no controlled reclaim, arbitrary write, or object replacement primitive is demonstrated.
* Memory corruption, strong corruption primitive: +2. SLUB freelist corruption and DMA page refcount corruption are concrete kernel memory corruption consequences, not merely a warning or NULL dereference.
* Real lifetime corruption: +1. Corrupting DMA page reference counts implies broken page lifetime/accounting semantics.
* Reliable kernel crash / strong DoS: +1. SLUB freelist corruption is likely to result in kernel crash or allocator failure.
* Privileged kernel/device-management memory corruption path: +1. The corruption occurs in a NIC RX DMA-adjacent driver ring path.
* Hard or unreliable trigger condition: -1. Triggering depends on qede_build_skb() returning NULL under memory pressure and on the RX BD ring state.
* Corruption primitive constrained / no demonstrated controlled payload: -1. The patch does not show attacker-controlled overwrite data, target selection, or a reliable reclaim primitive.

Conservative total: 6.

Paranoid adjustment:

* Integrity impact plausible: +1. Because the commit explicitly reaches SLUB freelist corruption, a higher manual-review score is defensible even without a demonstrated exploit primitive.

Paranoid total: 7.

## 3. Reachability analysis

A remote sender can potentially trigger the vulnerable receive path by sending traffic to a host using a qede network interface. No local account is required if the vulnerable interface is reachable, so the practical PR interpretation is PR:N for network exposure.

The path is not a generic TCP/IP core path, but it is an ordinary NIC RX data path for affected qede hardware. Exploitation is not expected to be trivial because it also requires memory pressure sufficient for qede_build_skb() allocation failure and the right ring-consumption sequence. Containers and namespaces are not central to triggering because the entry point is packet reception on the physical device.

Call-site confidence: medium-high. The patch shows the missing NULL checks before BD manipulation, and the commit message describes the caller-side consequence: additional BD recycling after one extra BD was already consumed.

## 4. Severity interpretation

This is not an ordinary Moderate NULL-check fix. The first-order trigger is allocation failure, but the downstream effect is BD ring desynchronization with DMA page reference count corruption and SLUB freelist corruption.

Realistically, the most likely impact is remote DoS through kernel crash on affected qede deployments. Theoretical exploitation beyond DoS is plausible enough for manual review because allocator freelist corruption can sometimes become security-relevant, but the patch does not demonstrate attacker-controlled overwrite, reclaim, object replacement, or a reliable privilege escalation path.

Overall this should be treated as Actionable Moderate at minimum and a Strong Important candidate for environments with exposed qede interfaces.

## 5. One-sentence report phrase

A qede RX error path can consume one extra BD after qede_build_skb() fails under memory pressure, desynchronizing the RX ring and potentially causing DMA page refcount corruption, SLUB freelist corruption, and remote kernel DoS on affected NICs.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.

Reason: this is network-reachable driver RX memory corruption with explicit SLUB freelist corruption risk, even though reliable exploitation likely requires memory pressure and the available patch does not prove a controlled privilege-escalation primitive.

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

Patch: qede: fix off-by-one in BD ring consumption on build_skb failure [ Upstream
Commit: ecc05d4b20220a09c9c69584fc46ca55248a374a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ecc05d4b20220a09c9c69584fc46ca55248a374a

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=ecc05d4b20220a09c9c69584fc46ca55248a374a

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

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

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

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: 6
  Paranoid ActionableScore: 7

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

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