{"cve":"CVE-2023-54089","nvd":{"published":"2025-12-24T13:16:10.767","modified":"2026-06-17T06:46:46.940","status":"Deferred","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_pmem: add the missing REQ_OP_WRITE for flush bio\n\nWhen doing mkfs.xfs on a pmem device, the following warning was\n\n ------------[ cut here ]------------\n WARNING: CPU: 2 PID: 384 at block/blk-core.c:751 submit_bio_noacct\n Modules linked in:\n CPU: 2 PID: 384 Comm: mkfs.xfs Not tainted 6.4.0-rc7+ #154\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n RIP: 0010:submit_bio_noacct+0x340/0x520\n ......\n Call Trace:\n  <TASK>\n  ? submit_bio_noacct+0xd5/0x520\n  submit_bio+0x37/0x60\n  async_pmem_flush+0x79/0xa0\n  nvdimm_flush+0x17/0x40\n  pmem_submit_bio+0x370/0x390\n  __submit_bio+0xbc/0x190\n  submit_bio_noacct_nocheck+0x14d/0x370\n  submit_bio_noacct+0x1ef/0x520\n  submit_bio+0x55/0x60\n  submit_bio_wait+0x5a/0xc0\n  blkdev_issue_flush+0x44/0x60\n\nThe root cause is that submit_bio_noacct() needs bio_op() is either\nWRITE or ZONE_APPEND for flush bio and async_pmem_flush() doesn't assign\nREQ_OP_WRITE when allocating flush bio, so submit_bio_noacct just fail\nthe flush bio.\n\nSimply fix it by adding the missing REQ_OP_WRITE for flush bio. And we\ncould fix the flush order issue and do flush optimization later.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/c1dbd8a849183b9c12d257ad3043ecec50db50b3","https://git.kernel.org/stable/c/c7ab7e45ccef209809f8c2b00f497deec06b29c0","https://git.kernel.org/stable/c/e39e870e1e683a71d3d2e63e661a5695f60931a7"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:18:08.089039631+00:00"},"epss":{"cve":"CVE-2023-54089","score":0.00206,"percentile":0.10657,"date":"2026-10-31"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}