CVE-2025-38064: Linux kernel · virtio: break and reset virtio devices on device_shutdown()
Source GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in aee42f3d57bfa37b2716df4584edeecf63b9df4c : patch Linux kernel soon.
Data as of 30 Oct 2026, 16:33 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 7.8 |
|---|
- Patch
- Available – fixed in aee42f3d57bfa37b2716df4584edeecf63b9df4c, acdfe206be6c70ec55dc8bfdb1a22036d10fae26, 8bd2fa086a04886798b505f28db4002525895203 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- nvd.nist.gov/vuln/detail/CVE-2025-38064 (opens in a new tab)
- git.kernel.org/stable/c/0c03e32494dd0bbcc301523e5ae567c2f567a7d9 (opens in a new tab)
- git.kernel.org/stable/c/1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f (opens in a new tab)
- git.kernel.org/stable/c/8bd2fa086a04886798b505f28db4002525895203 (opens in a new tab)
- git.kernel.org/stable/c/acdfe206be6c70ec55dc8bfdb1a22036d10fae26 (opens in a new tab)
- git.kernel.org/stable/c/aee42f3d57bfa37b2716df4584edeecf63b9df4c (opens in a new tab)