CVE-2023-54089

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> virtio_pmem: add the missing REQ_OP_WRITE for flush bio<br /> <br /> When doing mkfs.xfs on a pmem device, the following warning was<br /> <br /> ------------[ cut here ]------------<br /> WARNING: CPU: 2 PID: 384 at block/blk-core.c:751 submit_bio_noacct<br /> Modules linked in:<br /> CPU: 2 PID: 384 Comm: mkfs.xfs Not tainted 6.4.0-rc7+ #154<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)<br /> RIP: 0010:submit_bio_noacct+0x340/0x520<br /> ......<br /> Call Trace:<br /> <br /> ? submit_bio_noacct+0xd5/0x520<br /> submit_bio+0x37/0x60<br /> async_pmem_flush+0x79/0xa0<br /> nvdimm_flush+0x17/0x40<br /> pmem_submit_bio+0x370/0x390<br /> __submit_bio+0xbc/0x190<br /> submit_bio_noacct_nocheck+0x14d/0x370<br /> submit_bio_noacct+0x1ef/0x520<br /> submit_bio+0x55/0x60<br /> submit_bio_wait+0x5a/0xc0<br /> blkdev_issue_flush+0x44/0x60<br /> <br /> The root cause is that submit_bio_noacct() needs bio_op() is either<br /> WRITE or ZONE_APPEND for flush bio and async_pmem_flush() doesn&amp;#39;t assign<br /> REQ_OP_WRITE when allocating flush bio, so submit_bio_noacct just fail<br /> the flush bio.<br /> <br /> Simply fix it by adding the missing REQ_OP_WRITE for flush bio. And we<br /> could fix the flush order issue and do flush optimization later.