{"uuid": "29fdf752-1f50-473e-bd2c-3f1b58cb698f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38064", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18717", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38064\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n Invalid read at addr 0x102877002, size 2, region '(null)', reason: rejected\n Invalid write at addr 0x102877A44, size 2, region '(null)', reason: rejected\n ...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.\n\ud83d\udccf Published: 2025-06-18T09:33:42.931Z\n\ud83d\udccf Modified: 2025-06-18T09:33:42.931Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/aee42f3d57bfa37b2716df4584edeecf63b9df4c\n2. https://git.kernel.org/stable/c/8bd2fa086a04886798b505f28db4002525895203", "creation_timestamp": "2025-06-18T10:40:19.000000Z"}