Skip to main content

Linux Kernel EUVDEUVD-2026-55356

| CVE-2026-68255 HIGH
2026-08-10 Linux GHSA-ww5r-hf7r-8fmv
7.7
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.7 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
vuln.today AI
6.8 MEDIUM

Backend-controlled attack justifies AV:L/PR:N; primary impact is memory disclosure (C:H), with A:L for possible but non-primary kernel panic risk.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 03:26 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.7 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:01 cve.org
HIGH 7.7
CVE Published
Aug 10, 2026 - 12:01 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

drm/virtio: bound EDID block reads to the response buffer

virtio_get_edid_block() validates the read offset only against the device-supplied resp->size field, never against the fixed-size resp->edid array. The EDID block index is driven by the device-supplied extension count, so a malicious virtio-gpu backend can advertise a large size together with a high block count and read far past the array into adjacent kernel memory, which is then surfaced in the parsed EDID (an out-of-bounds read / info leak).

Also reject any read whose end exceeds the size of the edid array. Conforming EDID responses stay within the array and are unaffected.

AnalysisAI

Out-of-bounds read in the Linux kernel drm/virtio driver allows a malicious virtio-gpu backend to leak adjacent guest kernel memory by returning a crafted EDID response with an inflated size and extension block count. Guests running Linux 5.0 through multiple unpatched stable branches are affected wherever virtio-gpu is in use, covering the majority of QEMU/KVM-based cloud VM deployments. No public exploit code is identified at time of analysis, and EPSS at 0.21% (11th percentile) reflects the high-privilege prerequisite of backend control, though the risk is material in adversarial multi-tenant cloud environments.

Technical ContextAI

The vulnerability exists in virtio_get_edid_block() within the Linux kernel's DRM (Direct Rendering Manager) virtio-gpu paravirtualized display driver. EDID (Extended Display Identification Data) is a binary metadata format through which displays advertise their capabilities; in virtualized guests, this data is fetched from the hypervisor-controlled virtio-gpu backend via a shared-memory response buffer. The function validates the read offset against the device-supplied resp->size field - a value entirely under backend control - but never against the actual fixed-size bounds of the resp->edid array. The EDID extension block count, also backend-supplied, drives the block index loop. A crafted response with inflated size and a high extension count causes the kernel to iterate past the array boundary into adjacent kernel memory, returning that data as part of the parsed EDID. The CPE (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*) spans all Linux versions from 5.0 onward. No formal CWE is assigned, but the root cause is a classic missing bounds check against the actual buffer size - logically CWE-125 (Out-of-bounds Read) - exacerbated by trusting device-supplied length fields without independent verification.

RemediationAI

The primary remediation is upgrading to a patched Linux kernel: 6.6.148, 6.12.101, 6.18.42, 7.1.6, or 7.2-rc2, or applying the individual stable commits from git.kernel.org (9fc2a017c5d5, 2757e6e80309, 35be0e2c6862, 375c1934ef01, 4e1a53892ba7). The fix adds a hard check rejecting any EDID block read whose end offset would exceed the fixed-size resp->edid array, leaving conforming responses unaffected. Where immediate patching is not possible, a compensating control is to disable virtio-gpu EDID enumeration at the hypervisor configuration level (e.g., by restricting advertised virtio-gpu feature flags or disabling display output for headless workloads); the trade-off is loss of guest display functionality. Ensuring the hypervisor stack itself is up to date and properly isolated is the most impactful architectural control, since the vulnerability is only exploitable by a backend under attacker control.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-55356 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy