External risk intelligence

Improper GPU System Calls Lead to Out-of-Bounds Read and Write

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-74911

The vulnerability involves improper GPU system calls performed by software running on a local system. GPU driver operations and system calls are inherently local-only and require access to the physical device or local execution environment, making network-based exploitation from the public internet impossible in standard deployment scenarios.

Out-of-bounds Write

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical software vulnerability has been identified that could allow unauthorized access and manipulation of systems. This issue stems from how certain software handles system calls, potentially leading to data compromise. The main concern at this time is to confirm if our environment is exposed to this type of risk.

  • Software allows unauthorized system actions.
  • Matters if local or cloud software is affected.
  • Confirm relevance and exposure to this risk.

Attack Path

How an attacker could exploit the issue

An attacker could trigger this vulnerability by exploiting software running as a non-privileged user. This software, by improperly interacting with the GPU system, can enter an error state. This error path can lead to an out-of-bounds read and write, potentially allowing an attacker to compromise the system.

  • No privileges required to exploit.
  • Error path triggers out-of-bounds access.
  • Allows OOB read and write.

Live Threat

Current exploitation, exposure, and threat context

A non-privileged user running software could trigger an error path when making GPU system calls, potentially leading to an out-of-bounds read and write. This occurs when an error causes an array index to fall outside the expected bounds.

  • GPU system state and memory
  • Improper GPU system calls
  • Service instability or crashes

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability, impacting software running as a non-privileged user, requires immediate attention from teams responsible for the affected applications and the underlying infrastructure. The first step is to identify all instances of the vulnerable software, assess their exposure and criticality, and then determine the accountable owner to plan a coordinated remediation effort.

  • Application and infrastructure teams own this.
  • Verify non-privileged execution exposure.
  • Plan targeted remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the software affected by CVE-2026-74911?

This CVE concerns GPU drivers, which are specialized software components that act as translators between your operating system and the physical graphics hardware. They manage how applications interact with the GPU to render visuals or accelerate computations, essentially acting as the gatekeeper for hardware-level system calls.

What does an out-of-bounds read and write mean for this vulnerability?

This is a memory safety issue classified as CWE-787. It means the software mistakenly accesses or writes to memory locations outside the allocated area it is supposed to use. In this specific case, an error path fails to correctly manage an array index, allowing the program to read from or overwrite memory it should not be able to reach.

How is the error path triggered in CVE-2026-74911?

The flaw is triggered when software—even running with low, non-privileged permissions—initiates specific, improper system calls to the GPU. Crucially, normal or successful GPU operations do not trigger this bug; it specifically occurs when an unexpected error state forces the driver into a faulty cleanup process that miscalculates array bounds.

Is my system at risk from this GPU vulnerability?

According to Halo Surface Signal, this vulnerability is very unlikely to be reachable from the public internet. Because GPU driver operations are inherently local-only and require direct interaction with the physical device or a local execution environment, the threat is restricted to software running on the host system itself.

How should I respond to this vulnerability?

Start by identifying all hardware or software environments using these GPU drivers. Since local execution is required to trigger the issue, prioritize assessing systems where untrusted or non-privileged users have the ability to run arbitrary software, and coordinate with your infrastructure teams to plan updates.

References