---
id: CVE-2026-97915
title: |-
  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
summary: |-
  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 expect…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= d4e4257afa6ed5205eda993180401fc2c20e4b60 <
    6dbba89df4e842d226f5cd3dbc5e94533cfceea2
  - >-
    Linux >= d4e4257afa6ed5205eda993180401fc2c20e4b60 <
    5d06257359c9006a208fece9eb7f0a0e83e0cc92
  - >-
    Linux >= d4e4257afa6ed5205eda993180401fc2c20e4b60 <
    3d7130807009e9be6132c1394a2c7708a3ba39a7
  - >-
    Linux >= d4e4257afa6ed5205eda993180401fc2c20e4b60 <
    95bf070f3225dc7175725438c916ad321d42fe45
  - Linux 6.6
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:18.487'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97915'
references:
  - url: 'https://git.kernel.org/stable/c/3d7130807009e9be6132c1394a2c7708a3ba39a7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5d06257359c9006a208fece9eb7f0a0e83e0cc92'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6dbba89df4e842d226f5cd3dbc5e94533cfceea2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/95bf070f3225dc7175725438c916ad321d42fe45'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.891Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.