Description
In the Linux kernel, the following vulnerability has been resolved: virtio: break and reset virtio devices on device_shutdown() Hongyu reported a hang on kexec in a VM. QEMU reported invalid memory accesses during the hang. Invalid read at addr 0x102877002, size 2, region '(null)', reason: rejected Invalid write at addr 0x102877A44, size 2, region '(null)', reason: rejected ... It was traced down to virtio-console. Kexec works fine if virtio-console is not in use. The issue is that virtio-console continues to write to the MMIO even after underlying virtio-pci device is reset. Additionally, Eric noticed that IOMMUs are reset before devices, if devices are not reset on shutdown they continue to poke at guest memory and get errors from the IOMMU. Some devices get wedged then. The problem can be solved by breaking all virtio devices on virtio bus shutdown, then resetting them.
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/8bd2fa086a04886798b505f28db4002525895203 Patch
- git.kernel.org/stable/c/aee42f3d57bfa37b2716df4584edeecf63b9df4c Patch
- git.kernel.org/stable/c/0c03e32494dd0bbcc301523e5ae567c2f567a7d9
- git.kernel.org/stable/c/1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f
- git.kernel.org/stable/c/acdfe206be6c70ec55dc8bfdb1a22036d10fae26
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 17 · as of 7 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.