accel/ivpu: Limit firmware log name prints to field size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Limit firmware log name prints to field size
The name in struct vpu_tracing_buffer_header is a fixed-size array populated by the NPU firmware. It is expected to be NUL-terminated, but nothing on the host side enforces this, so printing it with an unbounded string conversion would read past the field if the terminator is ever missing and expose adjacent bytes of the shared tracing BO through dmesg and the debugfs FW log output.
Print at most as many characters as the name field holds, so the output never runs past it even if the string is not NUL-terminated.
From the CVE record · Linux
The Linux kernel’s accel/ivpu driver can read past a fixed-size firmware log name when the NPU firmware does not NUL-terminate it. This can expose adjacent bytes from the shared tracing buffer through dmesg and the debugfs firmware log; the input does not establish what access an attacker would need.
Engineers running Linux kernels with the accel/ivpu driver should check their kernel vendor’s advisory; affected versions are not specified.