Skip to main content
VulnerabilityPublished Updated

CVE-2025-38064: Linux kernel · virtio: break and reset virtio devices on device_shutdown()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in aee42f3d57bfa37b2716df4584edeecf63b9df4c : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-15.

Patch
Available – fixed in aee42f3d57bfa37b2716df4584edeecf63b9df4c, acdfe206be6c70ec55dc8bfdb1a22036d10fae26, 8bd2fa086a04886798b505f28db4002525895203 +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Linux kernel to aee42f3d57bfa37b2716df4584edeecf63b9df4c, acdfe206be6c70ec55dc8bfdb1a22036d10fae26, 8bd2fa086a04886798b505f28db4002525895203 or 1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ec3d41c4db4c21164332826ea8d812f94f2f6886, < aee42f3d57bfa37b2716df4584edeecf63b9df4c
Fixed in
  • aee42f3d57bfa37b2716df4584edeecf63b9df4c
LinuxLinuxAffected
  • ≥ ec3d41c4db4c21164332826ea8d812f94f2f6886, < acdfe206be6c70ec55dc8bfdb1a22036d10fae26
Fixed in
  • acdfe206be6c70ec55dc8bfdb1a22036d10fae26
LinuxLinuxAffected
  • ≥ ec3d41c4db4c21164332826ea8d812f94f2f6886, < 8bd2fa086a04886798b505f28db4002525895203
Fixed in
  • 8bd2fa086a04886798b505f28db4002525895203
LinuxLinuxAffected
  • ≥ ec3d41c4db4c21164332826ea8d812f94f2f6886, < 1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f
Fixed in
  • 1eaa83fd94ed5e40d43139025f5acb7bcfed3b5f
LinuxLinuxAffected
  • =2.6.24
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

Community reviews

Loading reviews…