accel/ivpu: Validate firmware log buffer metadata (CVE-2026-97916) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97916

accel/ivpu: Validate firmware log buffer metadata

Answer in brief

CVE-2026-97916 records a Unknown severity vulnerability in accel/ivpu: Validate firmware log buffer metadata. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=d4e4257afa6ed5205eda993180401fc2c20e4b60 <8ec3d6972f1440fae6c8dadd1859892775208759 \|\| >=d4e4257afa6ed5205eda993180401fc2c20e4b60 <40868f80a89199630b03d4457876f9a1feba0660 \|\| >=d4e4257afa6ed5205eda993180401fc2c20e4b60 <b1555f63ee1a680f280bc18e8dac416f250e2ec3 \|\| >=d4e4257afa6ed5205eda993180401fc2c20e4b60 <0724afc55c77c36c7feb9a7264b02aa7593c5c2d	8ec3d6972f1440fae6c8dadd1859892775208759, 40868f80a89199630b03d4457876f9a1feba0660, b1555f63ee1a680f280bc18e8dac416f250e2ec3, 0724afc55c77c36c7feb9a7264b02aa7593c5c2d
Linux/Linuxgeneric	6.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 8ec3d6972f1440fae6c8dadd1859892775208759 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.