All reports
Medium

kernel: nvdimm: pmem: keep PREFLUSH before data writes

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98161

Probability of exploitation in the next 30 days: 0.11%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: nvdimm: pmem: keep PREFLUSH before data writes pmem_submit_bio() records a REQ_PREFLUSH error, but continues to copy the bio data and can later overwrite the error with a successful REQ_FUA flush. That lets data writes run after a failed preflush and can complete the bio successfully despite the failed ordering barrier. Run the REQ_PREFLUSH flush synchronously before touching the bio data and complete the bio with the flush error if it fails. Keep asynchronous flush chaining for REQ_FUA. At that point, data copy has completed and the parent bio can wait for the chained flush bio.

A flaw was found in the Linux kernel's persistent memory (pmem) subsystem. When processing storage write requests, the driver continues copying data even if a preceding cache flush operation fails, potentially overwriting the error status and reporting success. A local user performing I/O operations on persistent memory devices could trigger this flaw, leading to silent data corruption or inconsistent storage states due to violated write ordering barriers.