CVE-2024-50030 drm/xe/ct: prevent UAF in send_recv()

High 7.8 Published Updated

A use-after-free vulnerability in the Linux kernel's Xe GPU driver allows attackers to potentially execute code or escalate privileges via race conditions.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-50030?

CVE-2024-50030 is a high-severity use after free vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/ct: prevent UAF in send_recv()

Ensure we serialize with completion side to prevent UAF with fence going out of scope on the stack, since we have no clue if it will fire after the timeout before we can erase from the xa. Also we have some dependent loads and stores for which we need the correct ordering, and we lack the needed barriers. Fix this by grabbing the ct->lock after the wait, which is also held by the completion side.

v2 (Badal): - Also print done after acquiring the lock and seeing timeout.

(cherry picked from commit 52789ce35c55ccd30c4b67b9cc5b2af55e0122ea)

Weakness: CWE-416

Which versions are affected by CVE-2024-50030?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-50030?

Apply the vendor's patch.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2024-50030 being exploited?

There is no known exploitation of CVE-2024-50030 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2024-50030, DEBIAN-CVE-2024-50030, GHSA-9g6j-fh54-mg8j, UBUNTU-CVE-2024-50030.

Is CVE-2024-50030 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free