Answer in brief
CVE-2024-38592 records a Unknown severity vulnerability in drm/mediatek: Init `ddp_comp` with devm_kcalloc(). 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 | >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <cf69d0af7db917b82aceaa44b7b1b9376609da22 || >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <9fe2cc3fa44f7ad7ba5f29c1a68b2b924c17b9b1 || >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33 | cf69d0af7db917b82aceaa44b7b1b9376609da22, 9fe2cc3fa44f7ad7ba5f29c1a68b2b924c17b9b1, 01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jun 19, 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/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn't reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn't hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it's suggested to only use the non-initting alloc functions if you really need to. Let's switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-38592 records a Unknown severity vulnerability in drm/mediatek: Init `ddp_comp` with devm_kcalloc(). 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 | >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <cf69d0af7db917b82aceaa44b7b1b9376609da22 || >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <9fe2cc3fa44f7ad7ba5f29c1a68b2b924c17b9b1 || >=01389b324c97ff8f04e9c33b9ee246084f9f6dd2 <01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33 | cf69d0af7db917b82aceaa44b7b1b9376609da22, 9fe2cc3fa44f7ad7ba5f29c1a68b2b924c17b9b1, 01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jun 19, 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/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn't reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn't hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it's suggested to only use the non-initting alloc functions if you really need to. Let's switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.
Quoted source text, attributed separately from HOL analysis.