CVE-2024-0092

What it actually does

Improper check or handling of exception conditions in the affected component can trigger a denial of service.

Why it matters to the business

Local denial of service may interrupt GPU-accelerated workloads and require manual intervention to restore service; low EPSS and no KEV status indicate limited immediate external risk despite the two-year publication age.

How an attack unfolds

An attacker with local low-privileged access supplies input that triggers an exception path the driver does not handle correctly, causing the driver to stop responding and denying service to legitimate GPU operations.

How to fix it

Update gitlab-org/gitlab to the fixed commit c8f3448a2f0cfb3c812fc4619e0f16bc3feb133b; apply vendor-supplied driver updates that address exception handling.

How to confirm the fix worked

Confirm the installed driver or GitLab component reports the fixed commit/version; re-execute exception-triggering test cases to verify service remains available.

Typical attack path

1. Obtain local low-privileged access on a Windows or Linux system with the vulnerable driver
2. Craft and submit input that exercises an improperly handled exception condition
3. Trigger the flaw to induce driver-level denial of service

How to detect it

Review system and driver logs for repeated exception or fault entries around GPU processes; look for sudden termination of rendering or compute workloads without corresponding user action.

What your security team should do

• Prioritize patching systems that run GPU workloads or host the listed GitLab package
• Monitor for local privilege-escalation chains that could increase the impact of this DoS
• Review logging configurations to capture driver fault events for future detection