Answer in brief
CVE-2024-49943 records a Unknown severity vulnerability in drm/xe/guc_submit: add missing locking in wedged_fini. 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 | >=8ed9aaae39f39130b7a3eb2726be05d7f64b344c <d88f9bab7e62dd0dbe983fa70cf040042a60cc84 || >=8ed9aaae39f39130b7a3eb2726be05d7f64b344c <790533e44bfc7af929842fccd9674c9f424d4627 | d88f9bab7e62dd0dbe983fa70cf040042a60cc84, 790533e44bfc7af929842fccd9674c9f424d4627 |
| Linux/Linuxgeneric | 6.11 | Not reported |
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/guc_submit: add missing locking in wedged_fini Any non-wedged queue can have a zero refcount here and can be running concurrently with an async queue destroy, therefore dereferencing the queue ptr to check wedge status after the lookup can trigger UAF if queue is not wedged. Fix this by keeping the submission_state lock held around the check to postpone the free and make the check safe, before dropping again around the put() to avoid the deadlock. (cherry picked from commit d28af0b6b9580b9f90c265a7da0315b0ad20bbfd)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49943 records a Unknown severity vulnerability in drm/xe/guc_submit: add missing locking in wedged_fini. 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 | >=8ed9aaae39f39130b7a3eb2726be05d7f64b344c <d88f9bab7e62dd0dbe983fa70cf040042a60cc84 || >=8ed9aaae39f39130b7a3eb2726be05d7f64b344c <790533e44bfc7af929842fccd9674c9f424d4627 | d88f9bab7e62dd0dbe983fa70cf040042a60cc84, 790533e44bfc7af929842fccd9674c9f424d4627 |
| Linux/Linuxgeneric | 6.11 | Not reported |
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/guc_submit: add missing locking in wedged_fini Any non-wedged queue can have a zero refcount here and can be running concurrently with an async queue destroy, therefore dereferencing the queue ptr to check wedge status after the lookup can trigger UAF if queue is not wedged. Fix this by keeping the submission_state lock held around the check to postpone the free and make the check safe, before dropping again around the put() to avoid the deadlock. (cherry picked from commit d28af0b6b9580b9f90c265a7da0315b0ad20bbfd)
Quoted source text, attributed separately from HOL analysis.