CVE-2024-6790 [Medium] | Security Vulnerability in 5th Gen Gpu Architecture …

Loop with Unreachable Exit Condition ('Infinite Loop') 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 non-privileged user process to make valid GPU memory processing operations, including via WebGL or WebGPU, to cause the whole system to become unresponsive.This issue affects Bifrost GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Valhall GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Arm 5th Gen GPU Architecture Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-14	0.02%	0.11%	+0.10%
2	2025-11-21	0.05%	0.02%	-0.04%
3	2025-11-18	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-14

0.02%

0.11%

+0.10%

2025-11-21

0.05%

0.02%

-0.04%

2025-11-18

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.1	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	4.2	[email protected]
4.0	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.5	1.4	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.1

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

4.2

[email protected]

4.0

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.5

1.4

134c704f-9b21-4f2e-91b3-4a467353bcc0

Affected software / configurations for CVE-2024-6790

Vendor	Product	Version	Raw CPE
arm	5th_gen_gpu_architecture_kernel_driver	>= r46p0, < r49p1	cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver::::::::
arm	5th_gen_gpu_architecture_kernel_driver	>= r50p0, < r52p0	cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver::::::::
arm	5th_gen_gpu_architecture_kernel_driver	r44p1	cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r44p1:::::::*
arm	bifrost_gpu_kernel_driver	>= r46p0, < r49p1	cpe:2.3:a:arm:bifrost_gpu_kernel_driver::::::::
arm	bifrost_gpu_kernel_driver	>= r50p0, <= r51p0	cpe:2.3:a:arm:bifrost_gpu_kernel_driver::::::::
arm	bifrost_gpu_kernel_driver	r44p1	cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r44p1:::::::*
arm	valhall_gpu_kernel_driver	>= r46p0, < r49p1	cpe:2.3:a:arm:valhall_gpu_kernel_driver::::::::
arm	valhall_gpu_kernel_driver	>= r50p0, < r52p0	cpe:2.3:a:arm:valhall_gpu_kernel_driver::::::::
arm	valhall_gpu_kernel_driver	r44p1	cpe:2.3:a:arm:valhall_gpu_kernel_driver:r44p1:::::::*

References for CVE-2024-6790

URL	Tags
https://developer.arm.com/Arm%20Security%20Center/Mali%20GPU%20Driver%20Vulnerabilities	Vendor Advisory

URL

CVE-2024-6790 | Mali GPU Kernel Driver can cause the whole system to become unresponsive

Exploit prediction scoring system (EPSS) score for CVE-2024-6790

Common vulnerability scoring system (CVSS) metrics for CVE-2024-6790

Weakness enumeration for CVE-2024-6790

Affected software / configurations for CVE-2024-6790

References for CVE-2024-6790