[CVE-2026-98615][MODERATE REGULAR] eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox [ Upstream

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

CVE: CVE-2026-98615
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox [ Upstream
Commit: ed4163f6ba9b52bfd6216d5215ee7b8eb5072411
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ed4163f6ba9b52bfd6216d5215ee7b8eb5072411
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98615
Analysis date: Fri, 23 Oct 2026 21:09:29 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
An incomplete fbnic mailbox flush sequence can leave staged device writes parked and prevent firmware teardown or recovery from completing, causing device-local availability loss without an established memory-corruption or security-boundary primitive.

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

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

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: NO

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

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

CVE-2026-98615	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98615 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE AEGIS_AS=1 LEGACY=MODERATE RESULT=SAME V39_AEGIS_ONE_STEP_UP=LOW->MODERATE (final reconciliation agrees; DECISION: both MODERATE)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-404;CWE-754;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'The fbnic firmware mailbox receive ring teardown can fail to complete because clearing BME stops writes to host memory while staged requests remain parked in the PUL write pipeline. Setting FLUSH without FLUSH_MODE does not drain those requests, so firmware can continue waiting for a flush that never finishes. For the CVSS the PR:H value is used because reliable triggering normally requires administrative control of the driver or device teardown and reset paths. The issue is not demonstrated to be reachable through ordinary network traffic. Impact is limited to availability of the affected device or its recovery path, with no supported UAF, OOB access, information disclosure, arbitrary write, or privilege escalation primitive. A persistent flush failure may leave the interface unavailable until another recovery operation or system restart. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.1 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 MODERATE 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 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and KPANIC_UNSUPPORTED_REMOVED and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 0.0 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	REMOTE READ INIT NETWORK HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

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

ActionableScore=1
PrimitiveClass=NONE
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 conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

Positive signals:

* +1 Availability impact. The incomplete mailbox write flush can leave firmware waiting indefinitely and prevent successful teardown or recovery of the affected network device.

Negative signals:

* No negative points. Host-administrator privilege, rare hardware, and difficult timing are not sufficiently established to justify penalties.

Important non-awarded signals:

* No UAF, OOB access, DMA overwrite, repeated release, stale reference, or kernel memory-corruption primitive is established.
* No reliable kernel panic or host-wide DoS is demonstrated. The supported consequence is device or recovery-path unavailability.
* No remote-reachability point. Ordinary network packets are not shown to invoke `fbnic_mbx_reset_desc_ring()` or control the flush state.
* No firmware-mediated attacker-input point. Firmware waits on the incorrect host-programmed flush sequence, but attacker control over firmware behavior is not established.
* No confidentiality, integrity, privilege-escalation, authorization-bypass, or protected-resource impact is established.
* V33 and V32 do not apply because there is no attacker-influenced active structured-state corruption or checksum-metadata write.
* B5-R does not apply. There is no heap OOB write, retry-accumulated offset, or later consumption of corrupted heap state.
* B3-PENDING does not apply. No shared-backing or file-backed write is present.
* B4-PENDING does not apply. The patch changes hardware flush behavior, not a DENY-to-ALLOW authorization decision.
* No additional availability point was awarded for the same device hang.

3. Reachability analysis

The vulnerable path is executed while tearing down the fbnic firmware mailbox receive ring. The supplied code does not establish whether an ordinary local user, a delegated management process, incoming traffic, automatic device recovery, or only a host administrator can reliably initiate the complete sequence.

The operation targets a physical fbnic device and writes device control registers. An unprivileged namespace-scoped trigger is not shown, and no relevant namespace capability check is visible. Therefore `HostAdminRequired` and `NamespaceScopedPrivilege` remain `UNKNOWN` rather than being inferred from typical driver-management deployments.

Prior availability of supported fbnic hardware and an initialized firmware mailbox is required. The issue is deterministic once the affected teardown path contains staged writes, but attacker control over that condition is not established. This is not a race and receives no timing penalty.

4. Primitive and severity interpretation

The exact defect is an incomplete hardware flush sequence. Clearing BME prevents writes from reaching host memory, while setting `AW_FLUSH` without `AW_FLUSH_MODE` leaves staged requests parked in the PUL write pipeline. Firmware can consequently wait for a completion that never occurs.

This is a device-state logic bug rather than active-object corruption or fixed stale storage. There is no concrete repeated release or refcount operation. There is also no evidence that the parked writes reach host memory after BME is cleared.

`PrimitiveClass=NONE` is appropriate because no memory-lifetime, ownership, authorization, or attacker-useful corruption primitive is established. The demonstrated consequence is a mailbox teardown or recovery hang affecting the device. Host panic, memory corruption, DMA corruption, privilege escalation, and remote exploitation remain unsupported.

`ImportantCandidate=NO` because there is no Important-preserving primitive or unresolved trust-boundary corruption chain. `AutoDowngradeAllowed=YES` because the evidence supports a device-local operational defect without a security-boundary primitive.

5. One-sentence report phrase

An incomplete fbnic mailbox flush sequence can leave staged device writes parked and prevent firmware teardown or recovery from completing, causing device-local availability loss without an established memory-corruption or security-boundary primitive.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a deterministic device flush and recovery defect, but it does not establish memory corruption, host-wide failure, remote reachability, authorization bypass, or privilege escalation.

7. Call-site confidence

Call-site confidence: medium

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

Patch: eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox [ Upstream
Commit: ed4163f6ba9b52bfd6216d5215ee7b8eb5072411
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ed4163f6ba9b52bfd6216d5215ee7b8eb5072411

Changed files:
  drivers/net/ethernet/meta/fbnic/fbnic_csr.h
  drivers/net/ethernet/meta/fbnic/fbnic_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=ed4163f6ba9b52bfd6216d5215ee7b8eb5072411

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

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

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