What is CVE-2026-9040?

CVE-2026-9040 is Mali GPU Kernel Driver allows denial of service or disclosure of sensitive information. The supplied enrichment data classifies it as Race Condition mapped to CWE-362 Race Condition.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-9040. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-9040 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

5 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-9040 using CVSS null, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

Race Conditionpublic exploit

CVE-2026-9040

CVE-2026-9040 — Mali GPU Kernel Driver allows denial of service or disclosure of sensitive information

A race condition vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to cause a denial of service or disclose sensitive information. This issue affects Bifrost GPU Kernel Driver: from r12p0 through r49p5, from r50p0 through r51p0, from r54p1 through r54p2; Valhall GPU Kernel Driver: from r19p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p5, from r50p0 through r54p3, r55p0.

Published Sep 8, 2026Updated Sep 8, 2026Sources: NVD, Arm Ltd (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Arm Ltd

11 products listed

CVSS base

Unscored

no source published a base score

Remediation

The vendor's own words where we have them.

This issue has been fixed in the following versions: Valhall GPU Kernel Driver: r56p0; Arm 5th Gen GPU Architecture Kernel Driver: r56p0. Arm partners are recommended to upgrade to the latest applicable version as soon as possible.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Arm Ltd	Bifrost GPU Kernel Driver	r12p0	Vulnerable
Arm Ltd	Bifrost GPU Kernel Driver	r50p0	Vulnerable
Arm Ltd	Bifrost GPU Kernel Driver	r54p1	Vulnerable
Arm Ltd	Valhall GPU Kernel Driver	r19p0	Vulnerable
Arm Ltd	Valhall GPU Kernel Driver	r50p0	Vulnerable
Arm Ltd	Valhall GPU Kernel Driver	r55p0	Vulnerable
Arm Ltd	Valhall GPU Kernel Driver	r56p0	Patched
Arm Ltd	Arm 5th Gen GPU Architecture Kernel Driver	r41p0	Vulnerable
Arm Ltd	Arm 5th Gen GPU Architecture Kernel Driver	r50p0	Vulnerable
Arm Ltd	Arm 5th Gen GPU Architecture Kernel Driver	r55p0	Vulnerable
Arm Ltd	Arm 5th Gen GPU Architecture Kernel Driver	r56p0	Patched

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)
DoS: Resource Consumption (Other)
DoS: Crash, Exit, or Restart

Mitigation: In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.

Weakness & attack patterns

CWE-362Race Condition

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-26 · Leveraging Race ConditionsCAPEC-29 · Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Initial · CVE published
Sep 8, 2026 · NVD
Added · GHSA-j8jv-6mvv-5vg8 published (unknown)
Sep 8, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 8, 2026 · SOCRadar CTI

References

3 on the record

support.arm.com/documentation/111552/1-0/?lang=en
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-9040
NVD
github.com/advisories/GHSA-j8jv-6mvv-5vg8
Exploit, Third Party Advisory

Elsewhere on this site

Arm Ltdevery CVE for this vendor
Race Conditionsame class
CWE-362other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-9040 is Mali GPU Kernel Driver allows denial of service or disclosure of sensitive information, a unscored vulnerability affecting Bifrost GPU Kernel Driver, Valhall GPU Kernel Driver, Arm 5th Gen GPU Architecture Kernel Driver from Arm Ltd. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-9040. Public exploit evidence is: 5 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.