[CVE-2026-89511][MODERATE REGULAR] qede: Fix NULL pointer dereference in TPA fragment processing

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-89511
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: qede: Fix NULL pointer dereference in TPA fragment processing
Commit: 7f911e208b3ca2c76d9f2bbba1f54b9403568c10
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7f911e208b3ca2c76d9f2bbba1f54b9403568c10
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89511
Analysis date: Fri, 11 Sep 2026 22:50:01 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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 REGULAR
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-89511	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89511 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-665;CWE-754;BEST CVSS score: '5.9';DESCR 'A NULL pointer dereference in the qede Rx TPA path can occur because qede_tpa_start did not save sw_rx_data_cons data into tpa_info buffer data. Under memory pressure an SKB allocation failure during TPA_START can leave a saved descriptor with a valid DMA mapping but a NULL data pointer, and later qede_tpa_end can recycle this ghost buffer back into the active Rx ring. When hardware reuses that ring slot, TPA continuation processing can pass a NULL page into qede_fill_frag_skb and crash the kernel. For the CVSS the PR:N is selected for the paranoid score because a remote peer does not need an account on the victim if it can send traffic to the affected qede interface, although reliable triggering also depends on memory pressure, TPA being enabled, and QLogic qede hardware. The issue is network reachable through received traffic rather than a local ioctl or sysfs control path. Impact is denial of service via kernel panic.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	YES	REMOTE DANGER NULLPTR NETWORK SKB DMAorINTERRUPT KERNEL_PANIC_PLUS_UAF HARDWARE LINUS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

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

ActionableScore=3
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 3. No floor or cap applied.
* Raw paranoid score: 3
* Paranoid score: 3. No floor or cap applied.
* Final recommended bucket: **Borderline / manual review recommended**::

2. Signal breakdown

Positive signals:

* +2 Remote reachable / directly network-triggerable: the vulnerable path is in qede Rx TPA packet processing, and attacker-controlled received traffic can plausibly reach TPA continuation processing when the affected qede interface is exposed.
* +1 Reliable kernel crash / strong DoS: the commit reports a production kernel panic from NULL pointer dereference in qede_fill_frag_skb.

Negative signals:

* No negative privilege penalty: host-admin-equivalent privilege is not required for a remote peer to send traffic to the affected interface.
* No race/timing penalty: the issue is an ordered driver state bug under memory pressure, not a narrow race window.
* No rare-hardware penalty: qede hardware is hardware-specific, but the evidence does not establish a physical-only or unusually rare prerequisite sufficient for a scoring penalty.

Important non-awarded signals:

* RealUAF not awarded: the established primitive is a NULL data pointer recycled into an Rx ring, not a freed object being reused after lifetime end.
* Controlled reclaim not demonstrated.
* Arbitrary or directed kernel write not demonstrated.
* Confidentiality and integrity signals not awarded: the evidence supports crash/DoS only.
* Structured stale-object leverage not awarded: the stale or invalid state leads to NULL dereference, not meaningful post-reuse field consumption.
* Extra availability point not awarded: the same kernel panic is already counted as strong DoS.
* Concrete repeated release/refcount signal not awarded: there is no first release that may end object lifetime followed by a second lifetime/refcount mutation on the same dangling reference.

3. Reachability analysis

The evaluated attacker is a remote network peer able to send traffic to the affected qede interface. No local account or host-admin capability is needed for the traffic-sending part of the trigger, so HostAdminRequired=NO.

The complete trigger depends on deployment conditions: qede hardware, TPA/GRO behavior, an active Rx path, and memory pressure sufficient to make SKB allocation fail during TPA_START. These are meaningful reliability constraints, but they do not convert the issue into a local-only or host-admin-only vulnerability.

Namespace-scoped privilege is not relevant to the primary attacker model. The vulnerable operation is reached through device receive processing, not through a namespace-local privileged control-plane API.

Prior host setup exists in the ordinary operational sense that the NIC and driver must be configured and receiving traffic. This is not scored as a privilege prerequisite for the attacker because the bug is in runtime packet processing after the interface is deployed.

4. Primitive and severity interpretation

The exact primitive is an invalid driver descriptor state: qede_tpa_start fails to copy sw_rx_data_cons->data into tpa_info->buffer.data. If SKB allocation fails, qede_tpa_end later recycles a buffer with a valid DMA mapping but NULL data pointer back into the active Rx ring. When hardware reuses that slot, qede_fill_frag_skb receives a NULL page and the kernel crashes.

This is fixed stale/invalid driver storage rather than an active structured UAF. There is no concrete repeated lifetime/refcount mutation, no demonstrated controlled replacement, no attacker-shaped reclaimed object, and no callback or function-pointer consumption.

PrimitiveClass=CLASS_C because the demonstrated behavior is primarily crash/DoS from NULL pointer dereference. The demonstrated consequence is host kernel panic. Stronger consequences such as privilege escalation, arbitrary read/write, or information disclosure are speculative and not supported by the patch context.

ImportantCandidate=NO because the evidence does not establish a Class A primitive or a Class B lifetime/corruption primitive with unresolved exploitation leverage. AutoDowngradeAllowed=YES because this is a crash-only Class C driver state bug with no demonstrated memory corruption or security-boundary primitive, although manual review is still recommended due to network reachability.

Likely operational severity is Moderate-like remote DoS for exposed affected qede deployments, with practical exploitability depending on memory pressure and TPA behavior.

5. One-sentence report phrase

A NULL pointer dereference in qede TPA Rx fragment processing can allow a remote peer reaching the affected interface to trigger a kernel panic under memory pressure, with impact limited to denial of service based on the supplied evidence.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the issue is network reachable and causes a kernel crash, but the established primitive is NULL dereference only and does not show UAF, controlled corruption, information disclosure, or privilege escalation.

7. Call-site confidence

Call-site confidence: high

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

Patch: qede: Fix NULL pointer dereference in TPA fragment processing
Commit: 7f911e208b3ca2c76d9f2bbba1f54b9403568c10
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7f911e208b3ca2c76d9f2bbba1f54b9403568c10

Commit description:

Under memory pressure, the qede driver encounters NULL pointer
dereferences when processing TPA continuation fragments.

Commit 8a86339 ("qede: Add build_skb() support.") accidentally
dropped the assignment of tpa_info->buffer.data in qede_tpa_start().

When memory pressure causes an SKB allocation failure in qede_tpa_start(),
the driver sets tpa_start_fail = true and attempts to recycle the physical
page later in qede_tpa_end() via qede_reuse_page(). However, because
buffer.data was left uninitialized (NULL), qede_reuse_page() pushes a
"ghost" BD (valid DMA mapping but NULL data pointer) back into the
active Rx ring.

The next time the hardware uses this ring slot, it passes a NULL page
to qede_fill_frag_skb(), causing a kernel panic.

Example crash from production system:
 BUG: unable to handle kernel NULL pointer dereference at 0x8
 RIP: qede_fill_frag_skb+0x96/0x430 [qede]
 Call Trace:
   qede_rx_int+0xb06/0x1de0
   qede_poll+0x2f4/0x6c0
   __napi_poll+0x2d/0x130

Fix the root cause by restoring the tpa_info->buffer.data assignment
in qede_tpa_start(), ensuring valid pages are correctly tracked and
recycled. Additionally, update the stale comment for
struct qede_agg_info::buffer to reflect its current usage.

Fixes: 8a86339 ("qede: Add build_skb() support.")
Cc: stable@vger.kernel.org
Signed-off-by: Vaibhav Nagare <vnagare@redhat.com>
Link: https://patch.msgid.link/20260818073309.2266072-1-vnagare@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/ethernet/qlogic/qede/qede.h
  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=7f911e208b3ca2c76d9f2bbba1f54b9403568c10

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

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

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

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: unknown
  Paranoid ActionableScore: 3

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: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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