[CVE-2026-98726][MODERATE REGULAR] nvme-multipath: fix underflow in ANA log bounds checks

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

CVE: CVE-2026-98726
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: nvme-multipath: fix underflow in ANA log bounds checks
Commit: 03a0c21f0fd7a872953aae5714303d8f38d1e567
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=03a0c21f0fd7a872953aae5714303d8f38d1e567
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98726
Analysis date: Sat, 24 Oct 2026 12:34:14 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
A malicious connected NVMe controller can exploit underflowed ANA bounds checks to make the host read beyond the ANA log buffer and potentially crash the kernel.

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

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

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-98726	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98726 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=2 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:L/PR:N/UI:N/S:U/C:L/I:L/A:H';CWE-191;CWE-125;*CWE-20;Other CVSS 'AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.6';DESCR 'The ANA log parser can read beyond ana_log_buf because its bounds checks subtract controller supplied object sizes before proving that those sizes fit in the remaining buffer. A malicious or compromised NVMe controller can advertise an inconsistent group count or namespace ID count and cause the host to dereference a truncated descriptor or walk an oversized namespace ID array. For the CVSS the PR:N value is used because an attacker controlling the connected storage controller does not need privileges on the affected host. AV:A reflects the required configured NVMe storage relationship and ANA multipath context rather than unrestricted Internet reachability. The established primitive is an out of bounds read that can crash the kernel. The paranoid vector allows limited confidentiality and integrity impact because adjacent kernel memory may be consumed as namespace IDs and can influence ANA path state, but there is no supported OOB write, UAF, arbitrary write, reliable disclosure, or proven privilege escalation primitive. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 7.6 and the production ActionableScore returned 3 with recommendation Borderline / manual review recommended. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE_KPANIC because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE_KPANIC to MODERATE because the ActionableScore threshold 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 INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS and DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 5.3 and ActionableScore 2 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 MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	MAYBE	OOB SIMPLEFIX NVME LOG IMPROVEONLY LINUS  INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED	-	-	checked

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

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

1. ActionableScore

* Raw base score: 3.
* Conservative score: 3; no floor or cap applied.
* Raw paranoid score: 3.
* Paranoid score: 3; downstream confidentiality or integrity effects are not sufficiently proven for another point.
* Final recommended bucket: **Borderline / manual review recommended**::

2. Signal breakdown

* +1 Firmware-mediated external influence: inconsistent ANA data is supplied by a malicious or compromised connected NVMe controller.
* +1 Weak/indirect corruption concern: underflowing `ana_log_size - object_size` permits an out-of-bounds read of truncated descriptors or namespace-ID data, which can be passed into parser processing.
* +1 Reliable kernel crash/strong DoS: dereferencing or walking beyond `ana_log_buf` plausibly causes a host kernel fault.
* No availability point beyond the same crash.
* No OOB-write, UAF, disclosure path, arbitrary write, controlled target, or authorization bypass is shown.
* No confidentiality or integrity point: adjacent memory may be interpreted as namespace IDs, but protected-data disclosure or unauthorized persistent path-state modification is not established.
* NEW52/B5-R does not apply: there is no confirmed retry-accumulated OOB write or later consumption of corrupted written state.

3. Reachability analysis

The triggering input comes from a configured NVMe multipath controller using ANA. An attacker controlling that connected controller needs no host UID, capability, or namespace privilege, so host-administrator privilege is not required. A pre-existing storage relationship and ANA context are required; this is adjacent/device-mediated rather than unrestricted remote reachability. No race, retry accumulation, special namespace path, or rare-hardware-only condition is shown.

4. Primitive and severity reading

The primitive is a size-subtraction underflow causing a heap-buffer out-of-bounds read. It is neither active-object lifetime corruption nor a write primitive. The shown consequence is crash/DoS; consumption of bogus namespace IDs is plausible, but a concrete protected-state integrity effect is unresolved. This supports CLASS_C, not an Important-preserving Class A/B primitive. Auto-downgrade is allowed, while manual review remains advisable due to controller-to-host input and downstream callback processing.

5. One-sentence report phrase

A malicious connected NVMe controller can exploit underflowed ANA bounds checks to make the host read beyond the ANA log buffer and potentially crash the kernel.

6. Manual review advice

MANUAL CHECK RECOMMENDED

Confirm callback behavior and whether out-of-bounds namespace IDs can produce a concrete host path-state effect beyond a fault.

7. Call-site confidence

Call-site confidence: medium

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

Patch: nvme-multipath: fix underflow in ANA log bounds checks
Commit: 03a0c21f0fd7a872953aae5714303d8f38d1e567
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=03a0c21f0fd7a872953aae5714303d8f38d1e567

Commit description:

The number of ANA groups advertised through Identify Controller sizes the
ANA log buffer. The ANA log header and group descriptors independently
supply the number of groups and namespace IDs to parse.

Both bounds checks subtract an untrusted object size from ana_log_size
before comparing the current offset. If the object is larger than the
buffer, the size_t subtraction underflows and lets the parser read beyond
ana_log_buf.

Check the current offset before the first subtraction and compare each
object size with the remaining buffer instead. This rejects inconsistent
ANA data before dereferencing a truncated group descriptor or walking an
oversized namespace ID array.

Fixes: 0d0b660 ("nvme: add ANA support")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Daehyeon Ko <4ncienth@gmail.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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=03a0c21f0fd7a872953aae5714303d8f38d1e567

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

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

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

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