CVE-2026-98161: nvdimm: pmem: keep PREFLUSH before data writes
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 22d1f4dcdc9c6d0295c6db0c8933126098b14e05, 72561ca1ab96f0f0f32737a6171641e05a318538, 770a90c2127220f0fc194ce909ad4f0842e141cb; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 22d1f4dcdc9c6d0295c6db0c8933126098b14e05, 72561ca1ab96f0f0f32737a6171641e05a318538, 770a90c2127220f0fc194ce909ad4f0842e141cb; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-754
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.3 and later · before 6.18.52
- linux linux kernel6.19 and later · before 7.2.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.3affected
- c5d4355d10d414a96ca870b731756b89d068d57a and later · before 22d1f4dcdc9c6d0295c6db0c8933126098b14e05affected · git
- c5d4355d10d414a96ca870b731756b89d068d57a and later · before d34c30bc994328d9cf6749b2e9a32aabd08fd076affected · git
- c5d4355d10d414a96ca870b731756b89d068d57a and later · before 770a90c2127220f0fc194ce909ad4f0842e141cbaffected · git
- c5d4355d10d414a96ca870b731756b89d068d57a and later · before 72561ca1ab96f0f0f32737a6171641e05a318538affected · git
- c5d4355d10d414a96ca870b731756b89d068d57a and later · before c644a2f8fef5618fcf453c591177700fd07dd024affected · git
- before 5.3not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.112 and later · up to and including 6.12.*not affected · semver
- 6.18.52 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-100079Sep 25, 2026 · usb: typec: ucsi: unregister debugfs entries on teardown22Monitor
- ← EarlierCVE-2026-98160Sep 25, 2026 · staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init()22Monitor
- Later →CVE-2026-98162Sep 25, 2026 · smb/server: fix tree connection leak in smb2_tree_connect()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 22d1f4dcdc9c6d0295c6db0c8933126098b14e05 | Vendor (CNA) |
| Linux Linux | 72561ca1ab96f0f0f32737a6171641e05a318538 | Vendor (CNA) |
| Linux Linux | 770a90c2127220f0fc194ce909ad4f0842e141cb | Vendor (CNA) |
| Linux Linux | c644a2f8fef5618fcf453c591177700fd07dd024 | Vendor (CNA) |
| Linux Linux | d34c30bc994328d9cf6749b2e9a32aabd08fd076 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39682385 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2026-31637154 days apartrxrpc: reject undecryptable rxkad response tickets39Monitor
- CVE-2026-6384168 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring31Monitor
- CVE-2026-6384268 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring31Monitor
- CVE-2026-6384468 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring31Monitor
- CVE-2026-6384768 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 5.5
- Severity— → medium
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.