In the Linux kernel, the following vulnerability has been resolved: nvdimm: pmem: keep PREFLUSH...

zetlyn/cve-ghsa vulnerability ghsa GHSA-rj67-jfhc-gr45 cve CVE-2026-98161 known 2026-09-25

https://github.com/advisories/GHSA-rj67-jfhc-gr45

Properties

severityunknown
receipt
Source
GitHub advisories
Its words
unknown
Read by
field:severity
Said since
2026-09-28 11:44 UTC
Last answered
2026-10-04 18:15 UTC
Original
open at the source
What the source handed over
{
  "credits": [],
  "cve_id": "CVE-2026-98161",
  "cvss": {
    "score": null,
    "vector_string": null
  },
  "cvss_severities": {
    "cvss_v3": {
      "score": 0.0,
      "vector_string": null
    },
    "cvss_v4": {
      "score": 0.0,
      "vector_string": null
    }
  },
  "cwes": [],
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm: pmem: keep PREFLUSH before data writes\n\npmem_submit_bio() records a REQ_PREFLUSH error, but continues to copy the\nbio data and can later overwrite the error with a successful REQ_FUA flush.\nThat lets data writes run after a failed preflush and can complete the bio\nsuccessfully despite the failed ordering barrier.\n\nRun the REQ_PREFLUSH flush synchronously before touching the bio data and\ncomplete the bio with the flush error if it fails. Keep asynchronous flush\nchaining for REQ_FUA. At that point, data copy has completed and the parent\nbio can wait for the chained flush bio.",
  "epss": {
    "percentage": 0.00155,
    "percentile": 0.03913
  },
  "ghsa_id": "GHSA-rj67-jfhc-gr45",
  "github_reviewed_at": null,
  "html_url": "https://github.com/advisories/GHSA-rj67-jfhc-gr45",
  "identifiers": [
    {
      "type": "GHSA",
      "value": "GHSA-rj67-jfhc-gr45"
    },
    {
      "type": "CVE",
      "value": "CVE-2026-98161"
    }
  ],
  "nvd_published_at": "2026-09-25T14:17:27Z",
  "published_at": "2026-09-25T15:31:49Z",
  "references": [
    "https://nvd.nist.gov/vuln/detail/CVE-2026-98161",
    "https://git.kernel.org/stable/c/72561ca1ab96f0f0f32737a6171641e05a318538",
    "https://git.kernel.org/stable/c/770a90c2127220f0fc194ce909ad4f0842e141cb",
    "https://git.kernel.org/stable/c/c644a2f8fef5618fcf453c591177700fd07dd024",
    "https://github.com/advisories/GHSA-rj67-jfhc-gr45"
  ],
  "repository_advisory_url": null,
  "severity": "unknown",
  "source_code_location": "",
  "summary": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm: pmem: keep PREFLUSH...",
  "type": "unreviewed",
  "updated_at": "2026-09-25T15:31:54Z",
  "url": "https://api.github.com/advisories/GHSA-rj67-jfhc-gr45",
  "vulnerabilities": [],
  "withdrawn_at": null
}

Text

In the Linux kernel, the following vulnerability has been resolved: nvdimm: pmem: keep PREFLUSH... 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.