CVE-2026-53205

Analyzed Analyzed - Analysis Complete

Bounds Check Bypass in Linux Kernel IVPU Driver

Publication date: 2026-06-25

Last updated on: 2026-07-02

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Add bounds checks for firmware log indices Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from firmware), clamp them to safe values instead of proceeding with invalid offsets. This prevents potential out-of-bounds buffer access when firmware supplies invalid log indices.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-25

Last Modified

2026-07-02

Generated

2026-07-15

AI Q&A

2026-06-25

EPSS Evaluated

2026-07-14

NVD

CVE-2026-53205

EUVD

EUVD-2026-39296

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.13 (inc) to 6.18.36 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.13 (exc)
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.12.30 (inc) to 6.12.94 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Impact Analysis

If exploited, this vulnerability could lead to out-of-bounds buffer access in the Linux kernel when processing firmware log indices.

Such out-of-bounds access might cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service.

Executive Summary

This vulnerability exists in the Linux kernel's accel/ivpu component, where the firmware log buffer's read and write indices were not properly validated.

Specifically, the indices used to access the firmware log buffer could be out-of-bounds if supplied incorrectly by the firmware.

The fix involves adding bounds checks to ensure these indices are within valid limits before use, clamping any invalid indices to safe values to prevent out-of-bounds buffer access.

Compliance Impact

The provided information does not specify any impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Hi! I’m here to help you understand CVE-2026-53205. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70