LiveActive security incident?Get immediate response
CVE Record

CVE-2026-5165: Virtio-win: virtio-win: memory corruption via use-after-free in virtio blk device reset

A flaw was found in virtio-win, specifically within the VirtIO Block (BLK) device. When the device undergoes a reset, it fails to properly manage memory, resulting in a use-after-free vulnerability. This issue could allow a local attacker to corrupt system memory, potentially leading to system instability or unexpected behavior.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-5165 is a memory safety flaw in Red Hat's virtio-win VirtIO Block driver handling device resets. A local attacker with high privileges could corrupt memory, causing instability or unexpected behavior. It is not listed in CISA KEV, and the provided sources do not show active exploitation.

Executive priority

Treat as a moderate-priority virtualization driver issue. Remediate through normal patch governance, with faster action for environments where many Windows guests depend on Red Hat virtio-win drivers or where local administrator access is broadly delegated.

Technical view

The flaw is a use-after-free in virtio-win's VirtIO BLK reset path, mapped to CWE-825. CVSS 3.1 is 6.7 with local attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to environments using Red Hat virtio-win packages associated with RHEL 9 or RHEL 10. The source bundle lists RHEL 8 as unaffected. Prioritize virtualization platforms or images distributing these drivers to Windows guests using VirtIO Block devices.

Exploitation context

The attacker must already have high local privileges. Public sources provided do not indicate exploitation in the wild, weaponized exploit availability, or KEV status. Business risk is mainly guest instability or memory corruption in affected virtualized workloads.

Researcher notes

Provided data does not include fixed versions, exploit proof, or detailed trigger conditions beyond device reset. Focus validation on package provenance, affected RHEL stream, and VirtIO BLK usage. Avoid assuming host escape or remote exploitation; sources only support local high-privilege impact.

Mitigation direction

  • Check Red Hat CVE guidance for fixed virtio-win package availability.
  • Prioritize updates when Red Hat publishes corrected packages or advisories.
  • Limit high-privilege local access inside affected guest systems.
  • Track GitHub PR 1493 for engineering context, not vendor-approved deployment.
  • Document RHEL 8 virtio-win assets as unaffected per provided source data.

Validation and detection

  • Inventory RHEL 9 and RHEL 10 virtio-win packages and repositories.
  • Identify Windows guests using VirtIO Block drivers from affected packages.
  • Compare installed package status with Red Hat CVE guidance.
  • Confirm RHEL 8 assets are not incorrectly flagged.
  • Monitor Red Hat Bugzilla 2453015 for status changes.
Prepared
Confidence
high
Sources
5

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.

cwe · low confidence lookup

CWE-825: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-5165 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
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
0Timeline events
0ADP providers
4Source 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
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2026-5165Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Enterprise Linux 10virtio-winaffected
Red HatRed Hat Enterprise Linux 8virtio-winunaffected
Red HatRed Hat Enterprise Linux 9virtio-winaffected
Weakness

CWE details

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

CWE-825 · source CWE mapping

Expired Pointer Dereference

Expired Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.