# CVE-2026-72089: accel/ivpu: Reject firmware log with size smaller than header

> A missing size check in the Linux kernel IVPU driver allows integer underflow, leading to out-of-bounds reads and potential denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72089, DEBIAN-CVE-2026-72089, GHSA-f4rx-vf72-pg97, UBUNTU-CVE-2026-72089

## What is CVE-2026-72089?

CVE-2026-72089 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

accel/ivpu: Reject firmware log with size smaller than header

fw_log_from_bo() validates the tracing buffer header_size and that the
log fits within the BO, but never checks that log->size is at least
log->header_size. fw_log_print_buffer() then computes:

  u32 data_size = log->size - log->header_size;

which underflows to a near-U32_MAX value when firmware reports a log whose
size is smaller than its header. That huge data_size defeats the
log_start/log_end bounds clamps added by commit dd1311bcf0e6 ("accel/ivpu:
Add bounds checks for firmware log indices"), so fw_log_print_lines() reads
far past the small real data region of the BO. A size of 0 also makes
fw_log_from_bo() advance the offset by 0, causing the callers to loop
forever on the same header.

Reject logs whose size is smaller than the header (which also rejects
size == 0).

## Which versions are affected by CVE-2026-72089?


## How do I fix CVE-2026-72089?

Apply the vendor's patch.

## Is CVE-2026-72089 being exploited?

There is no known exploitation of CVE-2026-72089 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72089 and fix it if it is affected.

What it is: CVE-2026-72089 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72089 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72089/ (Markdown: https://insights.sbomify.com/CVE-2026-72089/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72089
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72089
- OSV: https://osv.dev/vulnerability/CVE-2026-72089

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72089/
Summaries are generated and may contain mistakes; the official description above is the record.