CVE-2026-99687

Description

A flaw was found in the Linux kernel's vhost-scsi driver. This vulnerability can lead to information disclosure, allowing an attacker within a guest virtual machine to read uninitialized host kernel memory. When handling misaligned storage commands that transfer less data than requested, the driver copies uninitialized temporary memory buffers back to the guest without clearing them first. Consequently, sensitive host memory contents may be exposed to the guest operating system.

Statement

This vulnerability is rated as Moderate because, although it allows an unprivileged guest user to read uninitialized host kernel memory across the virtualization boundary, the exposure is confined to residual bounce buffer data without granting write capabilities or host denial of service. Default Red Hat Enterprise Linux virtualization deployments do not enable in-kernel vhost-scsi devices, relying on userspace QEMU virtio emulation instead. Consequently, systems are only exposed if administrators explicitly configure virtual machines with the vhost-scsi backend.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeChangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactNoneN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.