GPU Sparse Memory API Out-of-Bounds Write in Linux Kernel

Publication date: 2026-06-12

Last updated on: 2026-06-15

Assigner: imaginationtech

Description

Software installed and run as a non-privileged user may conduct intentional GPU sparse memory API calls to cause out of bounds write in the kernel. The product incorrectly indexes internal state when performing sparse allocation remapping.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-12

Last Modified

2026-06-15

Generated

2026-07-03

AI Q&A

2026-06-13

EPSS Evaluated

2026-07-02

NVD

CVE-2026-34195

EUVD

EUVD-2026-36605

Affected Vendors & Products

Currently, no data is known.

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

Executive Summary

This vulnerability occurs when software running as a non-privileged user makes intentional GPU sparse memory API calls that lead to an out of bounds write in the kernel. The issue arises because the product incorrectly indexes internal state during sparse allocation remapping, which can cause memory corruption in the kernel.

Impact Analysis

An out of bounds write in the kernel caused by this vulnerability can lead to system instability, crashes, or potentially allow an attacker to escalate privileges or execute arbitrary code with kernel-level permissions.

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

0/70