LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux virtio shutdown flaw can leave virtual devices accessing memory after their underlying device or IOMMU has been reset. During VM kexec or shutdown, this may cause hangs, invalid memory accesses, or wedged devices. The supplied CVSS score is 7.8.

Executive priority

Treat as high priority for virtualization environments that use kexec, virtio-console, or IOMMU-backed virtio. Accelerate patch verification for systems requiring reliable restart or failover. Where those conditions are absent, confirm exposure before emergency maintenance.

Technical view

During virtio bus shutdown, virtio-console and potentially other virtio devices could continue MMIO or guest-memory activity after virtio-pci or IOMMU reset. The kernel fix marks virtio devices broken before resetting them, preventing post-reset access. The supplied vector requires local access and low privileges.

Likely exposure

Exposure is most plausible in Linux virtual machines using virtio devices, particularly virtio-console, during kexec or shutdown sequences. The record lists affected Linux versions including 2.6.24, 6.14.9, and 6.15, but its version mapping is ambiguous. Distribution backports must be checked individually.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation. Available evidence describes a reported VM hang and QEMU-detected invalid memory accesses during kexec.

Researcher notes

The supplied evidence supports a shutdown-ordering flaw and a fix that breaks, then resets, virtio devices. It does not establish a practical exploitation method, affected distribution packages, or active attacks. The affected-version representation is insufficiently precise for fleet decisions without vendor confirmation.

Mitigation direction

  • Apply vendor-supported Linux kernel updates incorporating the linked stable fixes.
  • Prioritize guests using virtio-console, kexec, or IOMMU-backed virtio devices.
  • Check distribution advisories for fixed packages and kernel backport status.
  • Follow vendor guidance for temporary mitigations; the supplied sources name no general workaround.

Validation and detection

  • Inventory Linux kernel versions across virtual machines using virtio devices.
  • Identify guests using virtio-console, kexec workflows, or IOMMU-backed virtualization.
  • Compare installed kernels against distribution advisories and the linked stable commits.
  • Review controlled lifecycle-test logs for hangs, virtio errors, or invalid memory-access reports.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38064 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38064Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxec3d41c4db4c21164332826ea8d812f94f2f6886, ec3d41c4db4c21164332826ea8d812f94f2f6886unaffected
LinuxLinux2.6.24, 0, 6.14.9, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.