[CVE-2026-74384][MODERATE 7.0] nvme-multipath: fix flex array size in struct nvme_ns_head [ Upstream

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

CVE: CVE-2026-74384
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: nvme-multipath: fix flex array size in struct nvme_ns_head [ Upstream
Commit: 7e7b167e65610dfa7564d449474f4b477f9d4c1c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7e7b167e65610dfa7564d449474f4b477f9d4c1c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74384
Analysis date: Sat, 15 Aug 2026 21:24:03 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
An undersized flexible array in NVMe multipath can cause a slab out-of-bounds write when sparse NUMA node IDs are used to index `current_path[]`, leading to kernel crash risk and possible constrained heap corruption in storage path revalidation.

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

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

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 7.0
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-74384	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-131;CWE-122;Other CVSS 'AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.5';DESCR 'An out-of-bounds write can occur in the NVMe multipath host code because nvme_ns_head current_path is allocated using num_possible_nodes() but later indexed with the actual NUMA node ID. On systems with sparse NUMA node IDs this can allocate too few entries and later write a struct nvme_ns pointer beyond the end of the object during namespace scan or path revalidation. For the CVSS the PR:N is used for paranoid scoring because a malicious or compromised NVMe controller or NVMe over Fabrics target on the storage fabric may trigger namespace discovery without needing privileges on the victim once the host is configured to use it. The attack complexity remains high because it depends on sparse NUMA topology, NVMe multipath, and controlled timing or discovery behavior. Impact is at least denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to heap memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 5)	YES	WRITE KASAN OOB NVME HARDWARE  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	NO	NO	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Constrained kernel buffer overwrite: +1. The bug is a real slab out-of-bounds write of one `struct nvme_ns *` pointer past `current_path[]`, but the written value is kernel-derived and the target is not clearly attacker-selected.
* Reliable kernel crash / strong DoS: +1. KASAN shows a concrete slab-out-of-bounds write during `nvme_mpath_revalidate_paths()`, and a production kernel may crash or corrupt adjacent heap state.
* Privileged kernel/device-management memory corruption path: +1. The corruption occurs in NVMe host multipath namespace/path management, a trusted storage/device-management path.
* Important filesystem/storage path: +1. NVMe namespace discovery and multipath path selection are important storage availability and integrity paths.
* Rare AND difficult-to-reach subsystem/configuration: -1. The issue depends on sparse NUMA node IDs, observed on specific architectures such as powerpc, plus NVMe multipath.
* Requires admin/root/device configuration in typical deployments: -1. In many environments the affected path requires an already configured NVMe device or NVMe-oF connection, normally controlled by administrators.

Paranoid additional interpretation:

* Firmware-mediated or storage-fabric external influence: +1. A malicious or compromised NVMe controller or NVMe-oF target may influence namespace discovery or path revalidation once the host is configured to use it.
* Weak LPE concern: +1. The bug is a concrete heap OOB write, so manual review is warranted, but the primitive is constrained and does not show attacker-controlled payload, target selection, reclaim, or arbitrary write.
* Integrity impact plausible: +1. Heap metadata or adjacent kernel object corruption is plausible in the worst case, although not demonstrated as a controlled exploit primitive.

Not awarded:

* No full Remote reachable +2. This is storage-fabric or device-mediated, not a generic Internet/network packet parser.
* No Strong LPE +2. There is no demonstrated reclaim, arbitrary write, controlled overwrite, type confusion, or callback control.
* No Dirty-Pipe-like/page-cache ownership bypass. The patch does not show writes into shared file-backed pages or COW ownership violation.
* No Confidentiality point. There is no read-back or information disclosure path shown.

## 3. Reachability analysis

The immediate trigger is kernel-side NVMe namespace scan or multipath path revalidation on a system where NUMA node IDs are sparse and `current_path[]` was allocated using `num_possible_nodes()` instead of `nr_node_ids`. A normal local unprivileged user does not typically control this path directly.

In conservative deployments, triggering usually requires administrative control over NVMe device setup, NVMe-oF connection setup, or hardware/storage configuration. In a more paranoid storage-fabric model, a malicious or compromised NVMe controller or NVMe-oF target could influence namespace discovery after the victim host is already configured to connect to it.

Namespaces and containers usually do not lower the trigger privilege because NVMe host controller management is not normally delegated to unprivileged containers. The path is common within NVMe multipath deployments, but the sparse NUMA prerequisite makes the bug architecture and topology dependent.

Call-site confidence: high. The supplied trace shows the write in `nvme_mpath_revalidate_paths()` through `nvme_update_ns_info()`, `nvme_alloc_ns()`, and `nvme_scan_ns()`.

## 4. Severity interpretation

This is more than an ordinary Moderate correctness bug because it is a real slab out-of-bounds write in a trusted storage subsystem. However, the practical exploitability is constrained by sparse NUMA topology, NVMe multipath, and weak control over both the written pointer value and the overwritten target.

Realistically, this behaves like an actionable Moderate storage/kernel memory-corruption issue with strong DoS potential. In the paranoid interpretation, it becomes a Strong Important candidate for manual review because the primitive is a concrete heap OOB write and may be externally influenced through a malicious storage controller or NVMe-oF target.

## 5. One-sentence report phrase

An undersized flexible array in NVMe multipath can cause a slab out-of-bounds write when sparse NUMA node IDs are used to index `current_path[]`, leading to kernel crash risk and possible constrained heap corruption in storage path revalidation.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a concrete slab out-of-bounds write in a kernel storage path. The primitive appears constrained, but the combination of heap corruption, NVMe multipath, and possible device or storage-fabric influence makes it unsuitable for auto-close.

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

Patch: nvme-multipath: fix flex array size in struct nvme_ns_head [ Upstream
Commit: 7e7b167e65610dfa7564d449474f4b477f9d4c1c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7e7b167e65610dfa7564d449474f4b477f9d4c1c

Changed files:
  drivers/nvme/host/core.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=7e7b167e65610dfa7564d449474f4b477f9d4c1c

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

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

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

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: 4
  Paranoid ActionableScore: 6

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 7.0

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