CVE-2026-97915: accel/ivpu: Limit firmware log name prints to field size
accel/ivpu: Limit firmware log name prints to field size
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In accel/ivpu firmware log handling, print the name from struct vpu_tracing_buffer_header using a bounded string conversion limited to the name field size, including for dmesg and debugfs FW log output, so output cannot read past the fixed-size field when NUL termination is missing.
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.