virtio: break and reset virtio devices on device_shutdown()
CVE-2025-38064 · published 18 Jun 2025
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2025-38064?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: ec3d41c4db4c21164332826ea8d812f94f2f6886 to < acdfe206be6c70ec55dc8bfdb1a22036d10fae26, ec3d41c4db4c21164332826ea8d812f94f2f6886 to < 1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f, ec3d41c4db4c21164332826ea8d812f94f2f6886 to < aee42f3d57bfa37b2716df4584edeecf63b9df4c, ec3d41c4db4c21164332826ea8d812f94f2f6886 to < 8bd2fa086a04886798b505f28db4002525895203
- Linux Linux: 2.6.24
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/acdfe206be6c70ec55dc8bfdb1a22036d10fae26
- git.kernel.org/stable/c/1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f
- git.kernel.org/stable/c/aee42f3d57bfa37b2716df4584edeecf63b9df4c
- git.kernel.org/stable/c/8bd2fa086a04886798b505f28db4002525895203
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON