Answer in brief
CVE-2024-50030 records a Unknown severity vulnerability in drm/xe/ct: prevent UAF in send_recv(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.8 | Not reported |
| Linux/Linuxgeneric | >=dd08ebf6c3525a7ea2186e636df064ea47281987 <8ed7dd4c55e4fb21531a9645aeb66a30eaf43a46 || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <db7f92af626178ba59dbbcdd5dee9ec24a987a88 | 8ed7dd4c55e4fb21531a9645aeb66a30eaf43a46, db7f92af626178ba59dbbcdd5dee9ec24a987a88 |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50030 records a Unknown severity vulnerability in drm/xe/ct: prevent UAF in send_recv(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.8 | Not reported |
| Linux/Linuxgeneric | >=dd08ebf6c3525a7ea2186e636df064ea47281987 <8ed7dd4c55e4fb21531a9645aeb66a30eaf43a46 || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <db7f92af626178ba59dbbcdd5dee9ec24a987a88 | 8ed7dd4c55e4fb21531a9645aeb66a30eaf43a46, db7f92af626178ba59dbbcdd5dee9ec24a987a88 |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.