CVE-2023-54089
Last modified
CVE-2023-54089 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: virtio_pmem: add the missing REQ_OP_WRITE for flush bio When doing mkfs.xfs on a pmem device, the following warning was ------------[ cut here ]------------ WARNING: CPU: 2 PID: 384 at block/blk-core.c:751 submit_bio_noacct Modules linked in: CPU: 2 PID: 384 Comm: mkfs.xfs Not tainted 6.4.0-rc7+ #154 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:submit_bio_noacct+0x340/0x520 ...... Call Trace: <TASK> ? submit_bio_noacct+0xd5/0x520 submit_bio+0x37/0x60 async_pmem_flush+0x79/0xa0 nvdimm_flush+0x17/0x40 pmem_submit_bio+0x370/0x390 __submit_bio+0xbc/0x190 submit_bio_noacct_nocheck+0x14d/0x370 submit_bio_noacct+0x1ef/0x520 submit_bio+0x55/0x60 submit_bio_wait+0x5a/0xc0 blkdev_issue_flush+0x44/0x60 The root cause is that submit_bio_noacct() needs bio_op() is either WRITE or ZONE_APPEND for flush bio and async_pmem_flush() doesn't assign REQ_OP_WRITE when allocating flush bio, so submit_bio_noacct just fail the flush bio. Simply fix it by adding the missing REQ_OP_WRITE for flush bio. And we could fix the flush order issue and do flush optimization later.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: virtio_pmem: add the missing REQ_OP_WRITE for flush bio When doing mkfs.xfs on a pmem device, the following warning was ------------[ cut here ]------------ WARNING: CPU: 2 PID: 384 at block/blk-core.c:751 submit_bio_noacct Modules linked in: CPU: 2 PID: 384 Comm: mkfs.xfs Not tainted 6.4.0-rc7+ #154 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:submit_bio_noacct+0x340/0x520 ...... Call Trace: <TASK> ? submit_bio_noacct+0xd5/0x520 submit_bio+0x37/0x60 async_pmem_flush+0x79/0xa0 nvdimm_flush+0x17/0x40 pmem_submit_bio+0x370/0x390 __submit_bio+0xbc/0x190 submit_bio_noacct_nocheck+0x14d/0x370 submit_bio_noacct+0x1ef/0x520 submit_bio+0x55/0x60 submit_bio_wait+0x5a/0xc0 blkdev_issue_flush+0x44/0x60 The root cause is that submit_bio_noacct() needs bio_op() is either WRITE or ZONE_APPEND for flush bio and async_pmem_flush() doesn't assign REQ_OP_WRITE when allocating flush bio, so submit_bio_noacct just fail the flush bio. Simply fix it by adding the missing REQ_OP_WRITE for flush bio. And we could fix the flush order issue and do flush optimization later.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= b4a6bb3a67aa0c37b2b6cd47efc326eb455de674, < e39e870e1e683a71d3d2e63e661a5695f60931a7; >= b4a6bb3a67aa0c37b2b6cd47efc326eb455de674, < c7ab7e45ccef209809f8c2b00f497deec06b29c0; >= b4a6bb3a67aa0c37b2b6cd47efc326eb455de674, < c1dbd8a849183b9c12d257ad3043ecec50db50b3 |
| Linux | Linux | 6.3 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54089?
How severe is CVE-2023-54089?
How do I fix CVE-2023-54089?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54083In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54084In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54085In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2023-54086In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54087In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54088In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-5409HP is aware of a potential security vulnerability in HP t430…6.8
- CVE-2023-54090In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2023-54091In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54092In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2023-54093In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54094In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2023-54089?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
