Answer in brief
CVE-2024-49876 records a Unknown severity vulnerability in drm/xe: fix UAF around queue destruction. 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 | >=dd08ebf6c3525a7ea2186e636df064ea47281987 <272b0e78874586d6ccae04079d75b27b47705544 || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <421c74670b0f9d5c007f1276d3647aa58f407fde || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <2d2be279f1ca9e7288282d4214f16eea8a727cdb | 272b0e78874586d6ccae04079d75b27b47705544, 421c74670b0f9d5c007f1276d3647aa58f407fde, 2d2be279f1ca9e7288282d4214f16eea8a727cdb |
| Linux/Linuxgeneric | 6.8 | 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: fix UAF around queue destruction We currently do stuff like queuing the final destruction step on a random system wq, which will outlive the driver instance. With bad timing we can teardown the driver with one or more work workqueue still being alive leading to various UAF splats. Add a fini step to ensure user queues are properly torn down. At this point GuC should already be nuked so queue itself should no longer be referenced from hw pov. v2 (Matt B) - Looks much safer to use a waitqueue and then just wait for the xa_array to become empty before triggering the drain. (cherry picked from commit 861108666cc0e999cffeab6aff17b662e68774e3)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49876 records a Unknown severity vulnerability in drm/xe: fix UAF around queue destruction. 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 | >=dd08ebf6c3525a7ea2186e636df064ea47281987 <272b0e78874586d6ccae04079d75b27b47705544 || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <421c74670b0f9d5c007f1276d3647aa58f407fde || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <2d2be279f1ca9e7288282d4214f16eea8a727cdb | 272b0e78874586d6ccae04079d75b27b47705544, 421c74670b0f9d5c007f1276d3647aa58f407fde, 2d2be279f1ca9e7288282d4214f16eea8a727cdb |
| Linux/Linuxgeneric | 6.8 | 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: fix UAF around queue destruction We currently do stuff like queuing the final destruction step on a random system wq, which will outlive the driver instance. With bad timing we can teardown the driver with one or more work workqueue still being alive leading to various UAF splats. Add a fini step to ensure user queues are properly torn down. At this point GuC should already be nuked so queue itself should no longer be referenced from hw pov. v2 (Matt B) - Looks much safer to use a waitqueue and then just wait for the xa_array to become empty before triggering the drain. (cherry picked from commit 861108666cc0e999cffeab6aff17b662e68774e3)
Quoted source text, attributed separately from HOL analysis.