CVE-2026-97915: accel/ivpu: Limit firmware log name prints to field size
In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Limit firmware log name prints to field size
The name in struct vputracingbufferheader 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In accel/ivpu firmware log handling, limit name printing to the fixed size of the vpu_tracing_buffer_header name field so output never reads past the field when the NPU firmware omits a NUL terminator.
Event History
Frequently Asked Questions
What data could be exposed if the issue is triggered?
Adjacent bytes from the shared tracing buffer object could be disclosed through kernel dmesg output and the debugfs firmware log output when a firmware-provided log name lacks a NUL terminator.
What condition is required for the out-of-bounds read?
The NPU firmware must provide a tracing-buffer name that is not NUL-terminated. The affected host-side logging path previously used an unbounded string conversion when printing that fixed-size field.
How does the fix mitigate the issue?
The fix limits log-name output to the size of the fixed-length name field. This prevents printing from reading beyond that field even when the firmware does not include a terminator.