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

drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers

drm_dp_sideband_parse_remote_dpcd_read() reads num_bytes from the raw
message and then unconditionally does:

memcpy(bytes, &raw->msg[idx], num_bytes);

without checking that idx + num_bytes <= raw->curlen. raw->msg[] is
256 bytes; if a malicious or misbehaving MST hub sets num_bytes larger
than the remaining payload, the memcpy reads past the received data
into whatever follows in raw->msg[].

drm_dp_sideband_parse_remote_i2c_read_ack() has the same flaw (noted
with a /* TODO check */ comment since the code was introduced).

Fix both functions by using a single combined check
(idx + num_bytes > curlen) before each memcpy. Since num_bytes is u8,
it is always >= 0, so this strictly subsumes the simpler idx > curlen
form and no separate step is needed.

[added missing fixes tag]
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel, the functions that parse remote DisplayPort sideband replies lack bounds checks when copying data from the received packet. The code copies num_bytes bytes from a raw message buffer without confirming that the source offset plus num_bytes does not exceed the message length. Because num_bytes is an 8‑bit value, the missing check allows a malicious or buggy Multi‑Stream Transport hub to request a read that overflows the buffer, resulting in an out‑of‑bounds read. This vulnerability can expose unintended kernel memory contents to an attacker, enabling information disclosure or potential exploitation through a subsequent memory corruption path.

Affected Systems

The weakness appears in the Linux kernel DRM subsystem. No specific kernel versions are enumerated in the advisory; therefore, any kernel that implements the DisplayPort multi‑stream transport sideband logic and has not been updated to the patched code may be vulnerable. Attackers that can interact with the system via a DisplayPort connection that includes an MST hub pose the main risk.

Risk and Exploitability

The formal CVSS score is not provided in the advisory, but the nature of the flaw suggests a high severity. Since the EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, the exploitation probability is currently unknown, but the legitimate attack vector is through a connected MST hub that issues out‑of‑bounds read requests. Once the read occurs, the attacker can read arbitrary kernel memory; if further exploitation techniques are available, remote code execution could be achieved. Administrators should consider the risk high for systems exposed to external MST hardware.

Generated by OpenCVE AI on August 10, 2026 at 15:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that contains the corrected bounds checks for drm_dp_sideband_parse_remote_dpcd_read and drm_dp_sideband_parse_remote_i2c_read_ack.
  • If an immediate kernel upgrade is not feasible, restrict or remove the use of external multi‑stream transport hardware that can trigger sideband read requests, or reconfigure the DRM subsystem to disable unused DPCD/I2C sideband functionality.
  • Monitor kernel logs for unexpected DPCD/I2C read errors and audit connected display hardware for suspicious activity to detect potential exploitation attempts.

Generated by OpenCVE AI on August 10, 2026 at 15:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 15:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers drm_dp_sideband_parse_remote_dpcd_read() reads num_bytes from the raw message and then unconditionally does: memcpy(bytes, &raw->msg[idx], num_bytes); without checking that idx + num_bytes <= raw->curlen. raw->msg[] is 256 bytes; if a malicious or misbehaving MST hub sets num_bytes larger than the remaining payload, the memcpy reads past the received data into whatever follows in raw->msg[]. drm_dp_sideband_parse_remote_i2c_read_ack() has the same flaw (noted with a /* TODO check */ comment since the code was introduced). Fix both functions by using a single combined check (idx + num_bytes > curlen) before each memcpy. Since num_bytes is u8, it is always >= 0, so this strictly subsumes the simpler idx > curlen form and no separate step is needed. [added missing fixes tag]
Title drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T12:02:09.423Z

Reserved: 2026-07-30T09:28:09.379Z

Link: CVE-2026-68279

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T15:30:05Z

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer