virtio: break and reset virtio devices on device_shutdown()
Affects Linux kernel virtio devices bound to a driver at shutdown or kexec, with the reported kexec hang seen using virtio-console. Fixed in kernel 6.6.160, 6.12.114 and 6.14.9.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.6.160, 6.12.114, 6.14.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.24
- KernelLinux
From 2.6.24 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.14.9
References 5
Questions about CVE-2025-38064
What does this mean?
At shutdown or kexec, virtio devices that have a driver bound were not broken and reset before the system moved on. The fix makes the kernel break and reset those devices in device_shutdown(). The reported kexec hang occurred with virtio-console in use.Source: git.kernel.org
Am I affected, and how do I check?
Kernels from 2.6.24 up to the first fixed release in each branch: before 6.6.160, from 6.7.0 up to before 6.12.114, and from 6.13.0 up to before 6.14.9. Check the running version with uname -r. The fix only acts on virtio devices that have a driver bound at shutdown or kexec.Source: git.kernel.org
What should I do about it?
Update the kernel to 6.6.160, 6.12.114, 6.14.9 or a later release in the matching branch.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data