Answer in brief
CVE-2024-40924 records a Unknown severity vulnerability in drm/i915/dpt: Make DPT object unshrinkable. 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 | >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <327280149066f0e5f2e50356b5823f76dabfe86e || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <7a9883be3b98673333eec65c4a21cc18e60292eb || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <a2552020fb714ff357182c3c179abfac2289f84d || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <43e2b37e2ab660c3565d4cff27922bc70e79c3f1 | 327280149066f0e5f2e50356b5823f76dabfe86e, 7a9883be3b98673333eec65c4a21cc18e60292eb, a2552020fb714ff357182c3c179abfac2289f84d, 43e2b37e2ab660c3565d4cff27922bc70e79c3f1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 12, 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/i915/dpt: Make DPT object unshrinkable In some scenarios, the DPT object gets shrunk but the actual framebuffer did not and thus its still there on the DPT's vm->bound_list. Then it tries to rewrite the PTEs via a stale CPU mapping. This causes panic. [vsyrjala: Add TODO comment] (cherry picked from commit 51064d471c53dcc8eddd2333c3f1c1d9131ba36c)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-40924 records a Unknown severity vulnerability in drm/i915/dpt: Make DPT object unshrinkable. 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 | >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <327280149066f0e5f2e50356b5823f76dabfe86e || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <7a9883be3b98673333eec65c4a21cc18e60292eb || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <a2552020fb714ff357182c3c179abfac2289f84d || >=0dc987b699ce4266450d407d6d79d41eab88c5d0 <43e2b37e2ab660c3565d4cff27922bc70e79c3f1 | 327280149066f0e5f2e50356b5823f76dabfe86e, 7a9883be3b98673333eec65c4a21cc18e60292eb, a2552020fb714ff357182c3c179abfac2289f84d, 43e2b37e2ab660c3565d4cff27922bc70e79c3f1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 12, 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/i915/dpt: Make DPT object unshrinkable In some scenarios, the DPT object gets shrunk but the actual framebuffer did not and thus its still there on the DPT's vm->bound_list. Then it tries to rewrite the PTEs via a stale CPU mapping. This causes panic. [vsyrjala: Add TODO comment] (cherry picked from commit 51064d471c53dcc8eddd2333c3f1c1d9131ba36c)
Quoted source text, attributed separately from HOL analysis.