Answer in brief
CVE-2024-53133 records a Unknown severity vulnerability in drm/amd/display: Handle dml allocation failure to avoid crash. 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 | >=abd26a3252cbd1a3ae4e46d37596d176fe50b41a <874ff59cde8fc525112dda26b501a1bac17dde9f || >=abd26a3252cbd1a3ae4e46d37596d176fe50b41a <6825cb07b79ffeb1d90ffaa7a1227462cdca34ae || 2064f7529dfe0305d6fafda77fdf66701d428db5 || >=6.7.12 <6.8 | 874ff59cde8fc525112dda26b501a1bac17dde9f, 6825cb07b79ffeb1d90ffaa7a1227462cdca34ae, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Dec 4, 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/amd/display: Handle dml allocation failure to avoid crash [Why] In the case where a dml allocation fails for any reason, the current state's dml contexts would no longer be valid. Then subsequent calls dc_state_copy_internal would shallow copy invalid memory and if the new state was released, a double free would occur. [How] Reset dml pointers in new_state to NULL and avoid invalid pointer (cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-53133 records a Unknown severity vulnerability in drm/amd/display: Handle dml allocation failure to avoid crash. 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 | >=abd26a3252cbd1a3ae4e46d37596d176fe50b41a <874ff59cde8fc525112dda26b501a1bac17dde9f || >=abd26a3252cbd1a3ae4e46d37596d176fe50b41a <6825cb07b79ffeb1d90ffaa7a1227462cdca34ae || 2064f7529dfe0305d6fafda77fdf66701d428db5 || >=6.7.12 <6.8 | 874ff59cde8fc525112dda26b501a1bac17dde9f, 6825cb07b79ffeb1d90ffaa7a1227462cdca34ae, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Dec 4, 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/amd/display: Handle dml allocation failure to avoid crash [Why] In the case where a dml allocation fails for any reason, the current state's dml contexts would no longer be valid. Then subsequent calls dc_state_copy_internal would shallow copy invalid memory and if the new state was released, a double free would occur. [How] Reset dml pointers in new_state to NULL and avoid invalid pointer (cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c)
Quoted source text, attributed separately from HOL analysis.