CVE-2026-98161: Linux kernel · nvdimm: pmem: keep PREFLUSH before data writes
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d34c30bc994328d9cf6749b2e9a32aabd08fd076 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d34c30bc994328d9cf6749b2e9a32aabd08fd076, c644a2f8fef5618fcf453c591177700fd07dd024, 72561ca1ab96f0f0f32737a6171641e05a318538 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/22d1f4dcdc9c6d0295c6db0c8933126098b14e05 (opens in a new tab)
- git.kernel.org/stable/c/d34c30bc994328d9cf6749b2e9a32aabd08fd076 (opens in a new tab)
- git.kernel.org/stable/c/770a90c2127220f0fc194ce909ad4f0842e141cb (opens in a new tab)
- git.kernel.org/stable/c/72561ca1ab96f0f0f32737a6171641e05a318538 (opens in a new tab)
- git.kernel.org/stable/c/c644a2f8fef5618fcf453c591177700fd07dd024 (opens in a new tab)