Answer in brief
CVE-2026-68279 records a Unknown severity vulnerability in drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <22d9f7fc1aaabaf73d5f30e8b0c9aa814ecd6ed2 || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <04d953f50d61e542e94a5977822cc53735f8c0ce || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <533d9e2bede4aeefdc2a0561d7071cfede95958f || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <e6ef5455b06cb4e5d181aabcd723791587c79f12 || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <1a8f537f5a1eeac941f262fe73078d6b08ba83c0 | 22d9f7fc1aaabaf73d5f30e8b0c9aa814ecd6ed2, 04d953f50d61e542e94a5977822cc53735f8c0ce, 533d9e2bede4aeefdc2a0561d7071cfede95958f, e6ef5455b06cb4e5d181aabcd723791587c79f12, 1a8f537f5a1eeac941f262fe73078d6b08ba83c0 |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68279 records a Unknown severity vulnerability in drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <22d9f7fc1aaabaf73d5f30e8b0c9aa814ecd6ed2 || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <04d953f50d61e542e94a5977822cc53735f8c0ce || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <533d9e2bede4aeefdc2a0561d7071cfede95958f || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <e6ef5455b06cb4e5d181aabcd723791587c79f12 || >=ad7f8a1f9ced7f049f9b66d588723f243a7034cd <1a8f537f5a1eeac941f262fe73078d6b08ba83c0 | 22d9f7fc1aaabaf73d5f30e8b0c9aa814ecd6ed2, 04d953f50d61e542e94a5977822cc53735f8c0ce, 533d9e2bede4aeefdc2a0561d7071cfede95958f, e6ef5455b06cb4e5d181aabcd723791587c79f12, 1a8f537f5a1eeac941f262fe73078d6b08ba83c0 |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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]
Quoted source text, attributed separately from HOL analysis.