# accel/ivpu: Add bounds checks for firmware log indices

CVE record · `CVE-2026-53205`

- **Identifiers:** `CVE-2026-53205`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 25 Jun 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 25 Jun 2026, 08:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `0923a7d55a85179744926b7c11768a81679cc4d4 to before 5961c703414048f46818be8bbb11075a9a63fb4e` (git)
  - affected: `1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 to before 8ec70c0dbdf04392a26e03e38798a373934177be` (git)
  - affected: `1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 to before 535da9ad8420c3b686a642403d4147ff220255fd` (git)
  - affected: `1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 to before dd1311bcf0e62f0c515115f46a3813370f4a4bb1` (git)
  - affected: `6.12.30 to before 6.12.94` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.13`
  - unaffected: `before 6.13` (semver)
  - unaffected: `6.12.94 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.36 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.13 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 25 Jun 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-53205](https://www.cve.org/CVERecord?id=CVE-2026-53205)
- [NVD: CVE-2026-53205](https://nvd.nist.gov/vuln/detail/CVE-2026-53205)

### References from the CNA

- <https://git.kernel.org/stable/c/5961c703414048f46818be8bbb11075a9a63fb4e>
- <https://git.kernel.org/stable/c/8ec70c0dbdf04392a26e03e38798a373934177be>
- <https://git.kernel.org/stable/c/535da9ad8420c3b686a642403d4147ff220255fd>
- <https://git.kernel.org/stable/c/dd1311bcf0e62f0c515115f46a3813370f4a4bb1>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53205>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53205/>. Everything for agents: <https://agentprime.io/llms.txt>.
