accel/ivpu: Add bounds checks for firmware log indices
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Add bounds checks for firmware log indices
Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from firmware), clamp them to safe values instead of proceeding with invalid offsets.
This prevents potential out-of-bounds buffer access when firmware supplies invalid log indices.
From the CVE record · Linux
The Linux kernel's accel/ivpu firmware log handling did not validate read and write indices before using them. Invalid indices supplied by firmware could cause out-of-bounds buffer access. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the accel/ivpu component should check their exposure; affected versions are not specified.