drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd · < d5c70523cafa26ad2c7a37b612849abe2683baa8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers
Three sideband reply parsers read 16-bit fields as:
val = (raw->msg[idx] << 8) | (raw->msg[idx+1]);
and check bounds only after the fact. When idx == raw->curlen, raw->msg[idx+1] reads one byte past the received message data into the following struct fields (curchunk_len, curchunk_idx, curlen).
Affected functions: - drm_dp_sideband_parse_enum_path_resources_ack() full_payload_bw_number and avail_payload_bw_number fields - drm_dp_sideband_parse_allocate_payload_ack() allocated_pbn field - drm_dp_sideband_parse_query_payload_ack() allocated_pbn field
Fix by using a single combined check (idx + 2 > curlen) before each 2-byte read. Since the check is strictly tighter than idx > curlen, no separate step is needed.
[added fixes tag]
From the CVE record · Linux
Three Linux kernel DRM DP MST sideband reply parsers read 16-bit fields before checking whether both bytes are present. A truncated sideband reply can trigger a one-byte out-of-bounds read into adjacent structure fields. The input does not specify attacker access, authentication requirements, or user interaction.
Engineers running Linux kernels with the affected DRM DP MST sideband reply parsers should check their kernel versions.