{"uuid": "a74ac37f-afe3-4644-be73-98da490b6bb3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38074", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18707", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38074\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvhost-scsi: protect vq->log_used with vq->mutex\n\nThe vhost-scsi completion path may access vq->log_base when vq->log_used is\nalready set to false.\n\n    vhost-thread                       QEMU-thread\n\nvhost_scsi_complete_cmd_work()\n-> vhost_add_used()\n   -> vhost_add_used_n()\n      if (unlikely(vq->log_used))\n                                      QEMU disables vq->log_used\n                                      via VHOST_SET_VRING_ADDR.\n                                      mutex_lock(&vq->mutex);\n                                      vq->log_used = false now!\n                                      mutex_unlock(&vq->mutex);\n\n          QEMU gfree(vq->log_base)\n        log_used()\n        -> log_write(vq->log_base)\n\nAssuming the VMM is QEMU. The vq->log_base is from QEMU userpace and can be\nreclaimed via gfree(). As a result, this causes invalid memory writes to\nQEMU userspace.\n\nThe control queue path has the same issue.\n\ud83d\udccf Published: 2025-06-18T09:33:50.006Z\n\ud83d\udccf Modified: 2025-06-18T09:33:50.006Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ca85c2d0db5f8309832be45858b960d933c2131c\n2. https://git.kernel.org/stable/c/bd8c9404e44adb9f6219c09b3409a61ab7ce3427\n3. https://git.kernel.org/stable/c/c0039e3afda29be469d29b3013d7f9bdee136834\n4. https://git.kernel.org/stable/c/f591cf9fce724e5075cc67488c43c6e39e8cbe27", "creation_timestamp": "2025-06-18T10:40:04.000000Z"}