[CVE-2026-98161][MODERATE REGULAR] nvdimm: pmem: keep PREFLUSH before data writes [ Upstream

[CVE-2026-98161][MODERATE REGULAR] nvdimm: pmem: keep PREFLUSH before data writes [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98161
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: nvdimm: pmem: keep PREFLUSH before data writes [ Upstream
Commit: 770a90c2127220f0fc194ce909ad4f0842e141cb
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=770a90c2127220f0fc194ce909ad4f0842e141cb
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98161
Analysis date: Fri, 25 Sep 2026 10:33:46 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-98161	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98161 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L';CWE-703;CWE-754;CWE-252;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N';BEST CVSS score: '6.1';DESCR 'A failed REQ_PREFLUSH operation in the NVDIMM pmem block path could be ignored while data writes continue. A later successful REQ_FUA flush could overwrite the earlier error and cause the bio to complete successfully even though the required persistence ordering barrier failed. This can violate durability guarantees and may cause data corruption or inconsistent application state after power loss device reset or other flush failure conditions. For the CVSS the PR:L reflects that an attacker or faulty local workload needs write access to the affected pmem block device or a filesystem hosted on it. The issue is not network reachable. Impact is primarily integrity loss. The paranoid availability impact is limited to possible filesystem or application unavailability caused by corrupted persistent data.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 3)	YES	INIT MEMORY  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

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

ActionableScore=3
ActionableScoreLower=2
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 2
* Conservative score: 2
* Raw paranoid score: 3
* Paranoid score: 3
* Final recommended bucket: **Ordinary Moderate**::

Conservative arithmetic: +1 concrete integrity impact. +1 important persistent-storage path.

Paranoid arithmetic: conservative 2. +1 plausible distinct availability impact if corrupted ordering causes a filesystem or application to become unavailable after recovery.

No floor or cap was applied.

2. Signal breakdown

Positive signals:

* +1 Integrity plausible. A failed REQ_PREFLUSH can be hidden by a later successful REQ_FUA completion. The caller may receive success despite a failed required persistence barrier, which can violate write ordering and durability guarantees.
* +1 Important filesystem and storage path. The defect is in the pmem block path and can affect filesystems, databases, or other persistence-sensitive workloads using NVDIMM persistent memory.
* +1 paranoid only. Persistent-data inconsistency can plausibly make a filesystem, database, or application unavailable after recovery. This is distinct from the integrity consequence but is not directly demonstrated as a host-wide kernel DoS.

Important non-awarded signals:

* No memory corruption primitive is established. The patch changes flush error handling and write ordering only.
* No UAF, stale reference, double free, refcount misuse, OOB access, or lifetime violation is established.
* No arbitrary or directed write is established.
* No attacker-controlled payload or target is established.
* No remote reachability is established.
* No local unprivileged trigger point is awarded. A local workload can issue writes and flushes, but the supplied evidence does not establish that an unprivileged attacker can reliably induce the underlying NVDIMM flush failure.
* No authorization or security-boundary bypass is established.
* No confidentiality impact is established.
* No privilege escalation is established.
* No reliable kernel crash or host-wide DoS is established.
* No niche-subsystem or hardware penalty is applied. Persistent-memory hardware is a deployment constraint, but the evidence does not establish that it is rare enough or inaccessible enough to justify a negative score.

3. Reachability analysis

The vulnerable operation is reached through writes to an NVDIMM pmem block device with REQ_PREFLUSH semantics. A relevant workload may be a filesystem, database, or application that issues durability-sensitive writes and flushes.

The practical trigger also requires an actual preflush failure. The supplied patch establishes that such a failure was mishandled, but it does not establish that an attacker can intentionally induce that device or media failure through ordinary local writes.

Host-admin-equivalent privilege is not positively required by the supplied code, because writes may occur through a mounted filesystem. However, below-host-admin exploitation of the complete failure sequence is also not positively established. Therefore HostAdminRequired is UNKNOWN.

No namespace-scoped capability path is relevant or established. NamespaceScopedPrivilege is UNKNOWN.

No network, firmware, DMA, special ioctl, or external packet path is shown. There is no evidence of a remote trigger.

The analysis assumes a system already configured with an accessible pmem namespace and a filesystem or application using it. The patch does not establish whether prior host-administrative provisioning of the pmem device is necessary for an attacker-controlled scenario.

4. Primitive and severity interpretation

The exact defect is error-state loss and persistence-ordering failure. pmem_submit_bio can continue copying data after REQ_PREFLUSH fails, and a later successful REQ_FUA flush can overwrite the previously recorded failure state. The bio can therefore report success even though the ordering barrier required before the data write failed.

This is neither active structured-object corruption nor fixed stale-storage use. It is not a cleanup, destructor, RCU, refcount, ownership, or lifetime bug. There is no repeated release or lifetime mutation.

The demonstrated consequence is possible integrity loss for persistent data. A workload can believe data was safely ordered and persisted when the preflush failure should have caused the write to fail. Depending on upper-layer recovery behavior, this can produce application inconsistency, database durability violations, or filesystem-level inconsistency after reset or power-loss conditions.

The speculative consequence is limited application or filesystem unavailability after integrity damage. The patch does not support arbitrary file overwrite, cross-user data modification, privilege escalation, information disclosure, kernel memory corruption, or kernel code execution.

PrimitiveClass is NONE because no meaningful kernel corruption, lifetime, authorization, ownership, or active security-boundary primitive is established. ImportantCandidate is NO because the demonstrated issue is a persistence semantic and error-handling defect without a concrete attacker-controlled corruption or boundary-bypass mechanism. AutoDowngradeAllowed is YES because no unresolved Class A or Class B kernel-corruption primitive would be lost by ordinary prioritization.

Operationally, the issue matters most for deployments that rely on pmem durability guarantees, especially databases and filesystems with synchronous-write workloads. It should be handled as a data-integrity reliability issue rather than an Important-class kernel exploitation candidate.

5. One-sentence report phrase

A failed REQ_PREFLUSH operation in the NVDIMM pmem block path could be ignored while data writes continue and later complete successfully, violating persistence ordering and potentially causing data inconsistency after recovery.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Review is recommended for systems that use NVDIMM pmem for filesystems, databases, journals, or other durability-sensitive workloads, but the patch does not establish a kernel-corruption or privilege-escalation primitive.

7. Call-site confidence

Call-site confidence: medium

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

Patch: nvdimm: pmem: keep PREFLUSH before data writes [ Upstream
Commit: 770a90c2127220f0fc194ce909ad4f0842e141cb
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=770a90c2127220f0fc194ce909ad4f0842e141cb

Changed files:
  drivers/nvdimm/pmem.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=770a90c2127220f0fc194ce909ad4f0842e141cb

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

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

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