Answer in brief
CVE-2024-46705 records a Unknown severity vulnerability in drm/xe: reset mmio mappings with devm. 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 <b1c9fbed3884d3883021d699c7cdf5253a65543a || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <c7117419784f612d59ee565145f722e8b5541fe6 | b1c9fbed3884d3883021d699c7cdf5253a65543a, c7117419784f612d59ee565145f722e8b5541fe6 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Sep 13, 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: reset mmio mappings with devm Set our various mmio mappings to NULL. This should make it easier to catch something rogue trying to mess with mmio after device removal. For example, we might unmap everything and then start hitting some mmio address which has already been unmamped by us and then remapped by something else, causing all kinds of carnage.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-46705 records a Unknown severity vulnerability in drm/xe: reset mmio mappings with devm. 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 <b1c9fbed3884d3883021d699c7cdf5253a65543a || >=dd08ebf6c3525a7ea2186e636df064ea47281987 <c7117419784f612d59ee565145f722e8b5541fe6 | b1c9fbed3884d3883021d699c7cdf5253a65543a, c7117419784f612d59ee565145f722e8b5541fe6 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Sep 13, 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: reset mmio mappings with devm Set our various mmio mappings to NULL. This should make it easier to catch something rogue trying to mess with mmio after device removal. For example, we might unmap everything and then start hitting some mmio address which has already been unmamped by us and then remapped by something else, causing all kinds of carnage.
Quoted source text, attributed separately from HOL analysis.