drm/i915/hdcp: check streams[] bounds before overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e03187e12cae57c09b521b6f7dd7c7f9aa2b62e9 · < 984085c5b53572e2e03fd5fc4817e86ef1effc6e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/hdcp: check streams[] bounds before overflow
The data->streams[] overflow check is done after the buffer overflow has already happened. Move the overflow check before the write.
Side note, emitting a warning splat with a backtrace might be overkill here, but prefer not changing the behaviour other than not doing the overrun.
Discovered using AI-assisted static analysis confirmed by Intel Product Security.
(cherry picked from commit 9284ab3b6e776c315883ac2611283d263c9460fd)
From the CVE record · Linux
The Linux kernel’s drm/i915 HDCP code checks the bounds of data->streams[] only after a write has already overflowed the buffer. The input does not specify how an attacker could reach this code or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the drm/i915 HDCP code should check their installations; affected versions are not specified.