[CVE-2026-98727][MODERATE REGULAR] nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known [ Upstream

[CVE-2026-98727][MODERATE REGULAR] nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98727
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known [ Upstream
Commit: 44dc998c38fb5e153c3ed5665f1112661841c3f5
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=44dc998c38fb5e153c3ed5665f1112661841c3f5
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98727
Analysis date: Sun, 18 Oct 2026 23:15:54 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
An NVMe multipath ZNS namespace can advertise zoned support with a zero zone size, causing report-zones or write paths to derive an invalid shift from `ilog2(0)` and potentially fail I/O, while a host-wide crash remains unconfirmed.

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

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

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-98727	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98727 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';*CWE-20;CWE-682;CWE-758;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.3';DESCR 'The NVMe multipath namespace head can advertise BLK_FEAT_ZONED before valid zone information has been obtained from a path namespace. If the zone information query leaves the zone size at zero, report zones or write operations through the head can evaluate ilog2(0) and use an invalid shift value. This can produce incorrect zone calculations, failed I O, warnings, or a possible host kernel crash depending on the downstream path and kernel configuration. For the CVSS the PR:N value is used because a malicious or faulty NVMe controller reachable through the storage fabric can supply the relevant namespace state without holding privileges on the host. AV:A is used because NVMe storage targets are normally reachable through an adjacent or restricted storage network rather than the public Internet. The base impact is limited to availability because the provided code does not establish UAF, OOB write, information disclosure, or another memory corruption primitive. The paranoid score raises availability to A:H because a host wide failure from the invalid shift cannot be excluded without reviewing all downstream zone calculation paths. Automated impact decision path. The original SimpleNet classifier selected MODERATE. The primary LLM estimated paranoid CVSS 5.3 and the production ActionableScore returned 2 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. 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 V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 2.6 and ActionableScore 0 with primitive class CLASS_C and manual review RECOMMENDED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	MAYBE	SIMPLEFIX NVME LINUS  V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED	-	-	checked

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

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

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 2
* Paranoid score: 2
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

Conservative signals:

* +1 Availability impact realistic. The inconsistent zoned limits are consumed by zone-reporting or write operations, causing invalid calculations and potentially failed I/O.
* Total: 1.

Additional paranoid signal:

* +1 Firmware or device-mediated external influence. A faulty or malicious NVMe controller may supply the zero-zone-size state, although attacker control and complete remote reachability are not established by the patch.
* Total: 2.

Important signals not awarded:

* No OOB read or write, UAF, double release, stale pointer, arbitrary write, or controlled corruption is established.
* No reliable kernel crash point was awarded. The patch establishes a shift derived from `ilog2(0)`, but not a specific fatal downstream operation.
* No direct network-reachability point was awarded. NVMe transport, controller configuration, and prior host setup are unresolved.
* No confidentiality or integrity point was awarded.
* NEW52 B5-R does not apply. There is no confirmed heap OOB write, retry-accumulated offset, or later consumption of corrupted heap state.
* NEW53 B3-PENDING does not apply. No shared-backing write is present.
* V33 and V34 do not apply. There is no attacker-influenced write into active structured state or checksum metadata.
* B4-PENDING does not apply because there is no authorization decision or DENY-to-ALLOW transition.
* No privilege, race, rarity, or hardware penalty was applied because the supplied evidence does not positively establish the required conditions.

3. Reachability analysis

The vulnerable state requires an NVMe multipath ZNS namespace whose zone-information query leaves the zone size at zero while the namespace head still advertises `BLK_FEAT_ZONED`. A subsequent report-zones or write operation through the head reaches the invalid calculation.

A faulty or malicious NVMe controller could plausibly influence the zone information. For NVMe over Fabrics this may cross a storage-network trust boundary, but the patch does not establish that an untrusted remote target can independently create the complete configuration and trigger sequence.

Prior privileged setup is likely needed to configure the controller and multipath namespace, but the exact privilege needed for the final I/O operation is not shown. Therefore `HostAdminRequired=UNKNOWN`. No user-namespace or namespace-scoped capability path is established. The issue is not a race and does not require retry accumulation.

4. Primitive and severity interpretation

The exact primitive is inconsistent block-device capability state followed by invalid arithmetic using `ilog2(0)`. This is active invalid state, but it is not demonstrated memory corruption or a lifetime violation.

The patch-supported consequence is incorrect zone calculation and disruption of report-zones or write operations. Failed I/O and device-path unavailability are credible. A host kernel crash remains unresolved because the supplied context does not show a downstream fatal shift, invalid memory access, or panic.

This is `CLASS_C`, not Class A or Class B. `ImportantCandidate=NO` because no independent corruption, ownership, authorization, or cross-boundary integrity primitive is established. `AutoDowngradeAllowed=YES` because the demonstrated defect remains an invalid-state availability issue. Manual review is still recommended to inspect downstream users of the computed zone shift and determine whether any affected architecture can reach a fatal operation.

5. One-sentence report phrase

An NVMe multipath ZNS namespace can advertise zoned support with a zero zone size, causing report-zones or write paths to derive an invalid shift from `ilog2(0)` and potentially fail I/O, while a host-wide crash remains unconfirmed.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Review downstream zone-shift consumers and NVMe over Fabrics reachability to determine whether the invalid value can cause a host-wide fault rather than device-local I/O failure.

7. Call-site confidence

Call-site confidence: medium

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

Patch: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known [ Upstream
Commit: 44dc998c38fb5e153c3ed5665f1112661841c3f5
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=44dc998c38fb5e153c3ed5665f1112661841c3f5

Changed files:
  drivers/nvme/host/multipath.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=44dc998c38fb5e153c3ed5665f1112661841c3f5

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

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

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

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

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