CVE-2026-93067

drm/bridge: tc358767: clamp the reported AUX read size to the request

N/A
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/bridge: tc358767: clamp the reported AUX read size to the request tc_aux_transfer() clamps an AUX read to the payload limit: size_t size = min_t(size_t, DP_AUX_MAX_PAYLOAD_BYTES - 1, msg->size); After the transfer it replaces size with the byte count the controller reports in AUX_BYTES: if (size) size = FIELD_GET(AUX_BYTES, auxstatus); AUX_BYTES is GENMASK(15, 8), so it can be up to 255. Nothing clamps it back to the request. tc_aux_read_data() reads that many bytes into the 16-byte auxrdata stack buffer, then copies them into the caller buffer. A reported count of 255 makes the read run to 256 bytes and overruns both. The controller should never report more than it was asked to transfer, so this is defense in depth rather than a live hole. The reported count is only lightly trusted, and the check is cheap. Clamp it back to the request, the same way ti-sn65dsi86 does in commit aca58eac52b8 ("drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

12dfe7c4d9c53442efcb4113cff505f60d6549065.4
Vendor states this is fixed in 33c0b072e31dee98a754d9bd01800359dfeb9e8f (fixed)
Vendor states this is fixed in 424b762cc26d512e3e7421e57e41b4b55be2400b (fixed)
Vendor states this is fixed in 57c567e0e8aa76f6e3e8f39d7f40c20bc37e76af (fixed)
Vendor states this is fixed in 982caa744fce79d18f2920382aaeb0da821a6e73 (fixed)
Vendor states this is fixed in 9ff718df547372d70ca20ad8e66a3fb1300936b2 (fixed)
Vendor states this is fixed in dd6274706bec30d005bff0587a4262d01dc2775a (fixed)
Vendor states this is fixed in ebf00c51c9ac9188e2806a2b842418805ee879be (fixed)
Vendor states this is fixed in ec6444a00c49e6c2b5e9a507272a28126677f9ee (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card