{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54089 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54089 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54089 and fix it if it is affected.\n\nWhat it is: CVE-2023-54089 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-54089 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54089/ (Markdown: https://insights.sbomify.com/CVE-2023-54089/index.md)","id":"CVE-2023-54089","markdown":"https://insights.sbomify.com/CVE-2023-54089/index.md","name":"CVE-2023-54089","record":{"aliases":["BELL-CVE-2023-54089","DEBIAN-CVE-2023-54089","GHSA-v2v9-hx36-32x2","UBUNTU-CVE-2023-54089"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing operation flag in the Linux kernel virtio_pmem driver causes a kernel warning and potential denial of service during filesystem operations on persistent memory devices.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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  \u003cTASK\u003e\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"virtio_pmem: add the missing REQ_OP_WRITE for flush bio","id":"CVE-2023-54089","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"ixgbe: Fix panic during XDP_TX with \u003e 64 CPUs","id":"CVE-2023-54090"},"packages":[],"prev":{"headline":"blk-cgroup: hold queue_lock when removing blkg-\u003eq_node","id":"CVE-2023-54088"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A missing operation flag in the Linux kernel virtio_pmem driver causes a kernel warning and potential denial of service during filesystem operations on persistent memory devices.","url":"https://insights.sbomify.com/CVE-2023-54089/"}