[CVE-2026-98616][LOW] eth: fbnic: reset num_napi when the napi vectors are freed [ Upstream

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

CVE: CVE-2026-98616
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: eth: fbnic: reset num_napi when the napi vectors are freed [ Upstream
Commit: c5b5aee41b9f5ed0743344be1c7b544555fa3cb9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c5b5aee41b9f5ed0743344be1c7b544555fa3cb9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98616
Analysis date: Sat, 24 Oct 2026 02:51:42 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
Stale fbnic NAPI-vector accounting after failed suspend/resume recovery can cause a later remove or unbind operation to NULL-dereference and crash the kernel.

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

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

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-98616	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98616 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE_KPANIC)	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-672;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'The fbnic driver could retain a nonzero num_napi after its NAPI vectors and IRQs were freed. A failed PCIe error recovery or a partial __fbnic_open failure during resume can leave this stale state, and a later device remove or unbind can make fbnic_dbg_down dereference an invalid vector and trigger a NULL pointer fault and kernel crash. The demonstrated primitive is a NULL pointer dereference rather than an attacker controlled UAF, OOB access, or arbitrary write. For the CVSS the PR:H value reflects that reliable triggering normally requires administrative control over power management, PCIe recovery, or device unbind. For the CVSS the paranoid PR:L value covers delegated hardware management or a less privileged service able to initiate the affected lifecycle operations. The issue is local, hardware specific, and requires an uncommon failure sequence, with availability impact only. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to LOW because KP specialist did not establish a qualifying panic and the cross model evidence reconciliation rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and KPANIC_UNSUPPORTED_REMOVED and V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 1.9 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	REMOTE DANGER NULLPTR UAF NETWORK HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED	-	-	checked

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw base score: 1.
* Conservative score: 1; no floor or cap applied.
* Raw paranoid score: 1.
* Paranoid score: 1; no additional primitive is technically supported.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Reliable kernel crash/strong DoS: stale `num_napi` makes `fbnic_dbg_down()` walk freed vector slots, producing the documented NULL-pointer dereference.
* No UAF score: vectors were freed, but the demonstrated later operation dereferences an invalid/NULL vector entry at address `0x210`; no access to reclaimed object storage is established.
* No OOB-write score or B5-R profile: there is no retry-accumulated index, heap overwrite, or later consumption of overwritten structured state.
* No corruption/leverage bonus: no controlled reclaim, payload, target, callback, repeated release, arbitrary write, disclosure, or protected-state modification is shown.
* No extra availability point: it would duplicate the same kernel fault.
* No privilege, hardware-rarity, or hard-race penalty: administrative lifecycle control is plausible, but exact permissions, hardware rarity, and materially difficult timing are not proven.

3. Reachability analysis

The sequence requires an fbnic device, suspend teardown followed by failed PCIe recovery or partial resume-open failure, and eventual remove/unbind close. The supplied evidence does not establish whether a normal user, delegated device-management service, or only host administration can drive the complete sequence. There is no namespace-capability path, remote packet trigger, or attacker-controlled retry sequence shown. The uncommon ordered failure sequence is not itself proof of a hard race.

4. Primitive and severity reading

The exact defect is stale bookkeeping: `num_napi` remains nonzero after NAPI vectors and IRQs are freed. A later teardown walks invalid entries and reaches a NULL-offset dereference. This is active stale state, but the proven terminal operation is a crash-only invalid dereference rather than a real post-lifetime object access, OOB write, or independently useful corruption primitive. Thus it is CLASS_C, not an Important candidate, and automatic Moderate treatment is permissible.

No authorization guard changes DENY to ALLOW; B4-PENDING and protected-resource impact do not apply.

5. One-sentence report phrase

Stale fbnic NAPI-vector accounting after failed suspend/resume recovery can cause a later remove or unbind operation to NULL-dereference and crash the kernel.

6. Manual review advice

NO MANUAL CHECK NEEDED

The patch supports availability-only invalid-state behavior with no material corruption or security-boundary primitive.

7. Call-site confidence

Call-site confidence: high

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

Patch: eth: fbnic: reset num_napi when the napi vectors are freed [ Upstream
Commit: c5b5aee41b9f5ed0743344be1c7b544555fa3cb9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c5b5aee41b9f5ed0743344be1c7b544555fa3cb9

Changed files:
  drivers/net/ethernet/meta/fbnic/fbnic_pci.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=c5b5aee41b9f5ed0743344be1c7b544555fa3cb9

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

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

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

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