How severe is CVE-2026-45198?

CVE-2026-45198 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-45198 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-45198?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-45198 published?

CVE-2026-45198 was published on 2026-08-07.

CVE-2026-45198

CVE-2026-45198 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-822.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-822
Published: 2026-08-07
Last modified: 2026-08-07

Description

Kernel software from a non-secure operating system on a platform with Trusted Execution Environment support, may cause GPU Firmware to boot up using data from non-secure memory. The GPU thread of control (Firmware) uses a pointer from non-secure memory belonging to the Rich Execution Environment (REE) when saving or retrieving internal data between the tightly coupled private memory to main memory. An attacker with control over the REE kernel may modify the pointer value, corrupting the data used by the GPU Firmware.

Frequently asked questions

What is CVE-2026-45198?: Kernel software from a non-secure operating system on a platform with Trusted Execution Environment support, may cause GPU Firmware to boot up using data from non-secure memory. The GPU thread of control (Firmware) uses a pointer from non-secure memory belonging to the Rich Execution Environment (REE) when saving or retrieving internal data between the tightly coupled private memory to main memory. An attacker with control over the REE kernel may modify the pointer value, corrupting the data used by the GPU Firmware.
How severe is CVE-2026-45198?: CVE-2026-45198 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-45198 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-45198?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-45198 published?: CVE-2026-45198 was published on 2026-08-07.

References

https://www.imaginationtech.com/gpu-driver-vulnerabilities/

Other CWE-822 vulnerabilities

CVE-2025-50165 — Critical (CVSS 9.8): Untrusted pointer dereference in Microsoft Graphics Component allows an unauthorized attacker to execute code over a…
CVE-2023-1437 — Critical (CVSS 9.8): All versions prior to 9.1.4 of Advantech WebAccess/SCADA are vulnerable to use of untrusted pointers. The RPC arguments…
CVE-2026-48137 — Critical (CVSS 9.1): There is an untrusted pointer dereference vulnerability in the NI grpc-device sideband streaming API that may allow an…
CVE-2025-4993 — Critical (CVSS 9.1): Untrusted Pointer Dereference vulnerability in RTI Connext Professional (Core Libraries) allows Pointer…
CVE-2025-1255 — Critical (CVSS 9.1): Untrusted Pointer Dereference vulnerability in RTI Connext Professional (Core Libraries) allows Pointer…
CVE-2024-36461 — Critical (CVSS 9.1): Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.

Browse all CWE-822 vulnerabilities →