In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
nvmet: pci-epf: fix use-after-free in nvmet_pci_epf_exec_iod_work()<\/p>\n
nvmet_pci_epf_exec_iod_work() submits an I\/O command with req->execute()
\nand then waits for the command to complete and transfers the data back
\nto the host. This wait is not needed for commands that do not transfer
\ndata from the device to the host. To decide whether that wait is needed,
\nit reads iod->data_len and iod->dma_dir after calling req->execute().<\/p>\n
However, once req->execute() is called, the command may complete
\nasynchronously on another CPU. For commands that do not require a
\ndevice-to-host data transfer, nvmet_pci_epf_queue_response() calls
\nnvmet_pci_epf_complete_iod() directly, which can free the iod before it
\nreads iod->data_len and iod->dma_dir, resulting in the KFENCE use-after-
\nfree:<\/p>\n
BUG: KFENCE: use-after-free read in nvmet_pci_epf_exec_iod_work+0x288\/0x798 [nvmet_pci_epf]<\/p>\n
Use-after-free read at 0x00000000fdfa6d03 (in kfence-#63):
\n nvmet_pci_epf_exec_iod_work+0x288\/0x798 [nvmet_pci_epf]
\n process_one_work+0x15c\/0x4f0
\n worker_thread+0x18c\/0x30c
\n kthread+0x130\/0x140
\n ret_from_fork+0x10\/0x20<\/p>\n
kfence-#63: 0x00000000e3de0e71-0x00000000c938ad62, size=712, cache=kmalloc-1k<\/p>\n
allocated by task 10 on cpu 0 at 73.995480s (0.005122s ago):
\n mempool_kmalloc+0x1c\/0x28
\n mempool_alloc_noprof+0x40\/0x9c
\n nvmet_pci_epf_poll_sqs_work+0xd4\/0x344 [nvmet_pci_epf]
\n process_one_work+0x15c\/0x4f0
\n worker_thread+0x18c\/0x30c
\n kthread+0x130\/0x140
\n ret_from_fork+0x10\/0x20<\/p>\n
freed by task 131 on cpu 3 at 73.995521s (0.008385s ago):
\n mempool_kfree+0x10\/0x20
\n mempool_free+0x44\/0x64
\n nvmet_pci_epf_free_iod+0x88\/0x98 [nvmet_pci_epf]
\n nvmet_pci_epf_cq_work+0xfc\/0x280 [nvmet_pci_epf]
\n process_one_work+0x15c\/0x4f0
\n worker_thread+0x18c\/0x30c
\n kthread+0x130\/0x140
\n ret_from_fork+0x10\/0x20<\/p>\n
Fix this by referring to iod->data_len and iod->dma_dir before calling
\nreq->execute(). The remaining iod accesses such as iod->status are only
\nreached on the device-to-host read path. In this case,
\nnvmet_pci_epf_queue_response() signals iod->done instead of freeing the
\niod, so the iod stays valid.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
nvmet: pci-epf: fix use-after-free in nvmet_pci_epf_exec_iod_work()<\/p>\n
nvmet_pci_epf_exec_iod_work() submits an I\/O command with req-<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-17291","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/17291","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=17291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=17291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=17291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}