{"api_version":"1","generated_at":"2026-09-27T03:01:56+00:00","cve":"CVE-2026-97915","urls":{"html":"https://cve.report/CVE-2026-97915","api":"https://cve.report/api/cve/CVE-2026-97915.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97915","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97915"},"summary":{"title":"accel/ivpu: Limit firmware log name prints to field size","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Limit firmware log name prints to field size\n\nThe name in struct vpu_tracing_buffer_header is a fixed-size array\npopulated by the NPU firmware. It is expected to be NUL-terminated,\nbut nothing on the host side enforces this, so printing it with an\nunbounded string conversion would read past the field if the\nterminator is ever missing and expose adjacent bytes of the shared\ntracing BO through dmesg and the debugfs FW log output.\n\nPrint at most as many characters as the name field holds, so the output\nnever runs past it even if the string is not NUL-terminated.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:18","updated_at":"2026-09-25 11:17:18"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/95bf070f3225dc7175725438c916ad321d42fe45","name":"https://git.kernel.org/stable/c/95bf070f3225dc7175725438c916ad321d42fe45","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6dbba89df4e842d226f5cd3dbc5e94533cfceea2","name":"https://git.kernel.org/stable/c/6dbba89df4e842d226f5cd3dbc5e94533cfceea2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5d06257359c9006a208fece9eb7f0a0e83e0cc92","name":"https://git.kernel.org/stable/c/5d06257359c9006a208fece9eb7f0a0e83e0cc92","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3d7130807009e9be6132c1394a2c7708a3ba39a7","name":"https://git.kernel.org/stable/c/3d7130807009e9be6132c1394a2c7708a3ba39a7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97915","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97915","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 6dbba89df4e842d226f5cd3dbc5e94533cfceea2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 5d06257359c9006a208fece9eb7f0a0e83e0cc92 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 3d7130807009e9be6132c1394a2c7708a3ba39a7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 95bf070f3225dc7175725438c916ad321d42fe45 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97915","cve":"CVE-2026-97915","epss":"0.002000000","percentile":"0.088400000","score_date":"2026-09-26","updated_at":"2026-09-27 00:04:20"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/accel/ivpu/ivpu_fw_log.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"6dbba89df4e842d226f5cd3dbc5e94533cfceea2","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"5d06257359c9006a208fece9eb7f0a0e83e0cc92","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"3d7130807009e9be6132c1394a2c7708a3ba39a7","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"95bf070f3225dc7175725438c916ad321d42fe45","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/accel/ivpu/ivpu_fw_log.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Limit firmware log name prints to field size\n\nThe name in struct vpu_tracing_buffer_header is a fixed-size array\npopulated by the NPU firmware. It is expected to be NUL-terminated,\nbut nothing on the host side enforces this, so printing it with an\nunbounded string conversion would read past the field if the\nterminator is ever missing and expose adjacent bytes of the shared\ntracing BO through dmesg and the debugfs FW log output.\n\nPrint at most as many characters as the name field holds, so the output\nnever runs past it even if the string is not NUL-terminated."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:22:37.117Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/6dbba89df4e842d226f5cd3dbc5e94533cfceea2"},{"url":"https://git.kernel.org/stable/c/5d06257359c9006a208fece9eb7f0a0e83e0cc92"},{"url":"https://git.kernel.org/stable/c/3d7130807009e9be6132c1394a2c7708a3ba39a7"},{"url":"https://git.kernel.org/stable/c/95bf070f3225dc7175725438c916ad321d42fe45"}],"title":"accel/ivpu: Limit firmware log name prints to field size","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97915","datePublished":"2026-09-25T10:22:37.117Z","dateReserved":"2026-09-25T10:18:58.201Z","dateUpdated":"2026-09-25T10:22:37.117Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:18","lastModifiedDate":"2026-09-25 11:17:18","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97915","Ordinal":"1","Title":"accel/ivpu: Limit firmware log name prints to field size","CVE":"CVE-2026-97915","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97915","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Limit firmware log name prints to field size\n\nThe name in struct vpu_tracing_buffer_header is a fixed-size array\npopulated by the NPU firmware. It is expected to be NUL-terminated,\nbut nothing on the host side enforces this, so printing it with an\nunbounded string conversion would read past the field if the\nterminator is ever missing and expose adjacent bytes of the shared\ntracing BO through dmesg and the debugfs FW log output.\n\nPrint at most as many characters as the name field holds, so the output\nnever runs past it even if the string is not NUL-terminated.","Type":"Description","Title":"accel/ivpu: Limit firmware log name prints to field size"}]}}}