Categories
CVE-2026-11891 medium CVSS 5.1

Use-After-Free in Valhall GPU Userspace Driver (CVE-2026-11891)

Summary

Vulnerability in Valhall GPU Userspace Driver (CVE-2026-11891). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

Use After Free vulnerability in Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to perform valid GPU processing operations, including via WebGL or WebGPU, to access already freed memory.

This issue affects Valhall GPU Userspace Driver: from r46p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Userspace Driver: from r46p0 through r49p5, from r50p0 through r54p3, r55p0.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-11891 has been found in Valhall GPU Userspace Driver.
Risk of unauthorized operations or information disclosure. CVSS score: 5.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Valhall GPU Userspace Driver CVE-2026-11891" on the vendor's site.

CVE-2026-11891 (Valhall GPU Userspace Driver) — CWE-416 / CVSS v3 5.1
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Use-after-free (CWE-416) exists in Valhall GPU Userspace Driver.

📍 Affected scope

Check the vendor advisory for the affected versions of Valhall GPU Userspace Driver.

🔥 Severity

Severity: Medium (CVSS 5.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Valhall GPU Userspace Driver を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details