CVE-2024-38592
Last modified
CVE-2024-38592 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.8.12 |
| Linux | Linux Kernel | >= 6.9, < 6.9.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-38592?
How severe is CVE-2024-38592?
How do I fix CVE-2024-38592?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-38587In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-38588In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-38589In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-3859On 32-bit versions there were integer-overflows that led to …5.9
- CVE-2024-38590In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38591In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38593In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38594In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38595In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38596In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-38597In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-38598In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-38592?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
