CVE-2024-38549: drm/mediatek: Add 0 size check to mtk_drm_gem_obj
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: Add 0 size check to mtkdrmgemobj
Add a check to mtkdrmgeminit if we attempt to allocate a GEM object of 0 bytes. Currently, no such check exists and the kernel will panic if a userspace application attempts to allocate a 0x0 GBM buffer.
Tested by attempting to allocate a 0x0 GBM buffer on an MT8188 and verifying that we now return EINVAL.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.94-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.8.12-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-38549?
CVE-2024-38549 has been classified as a medium severity vulnerability due to potential kernel panics impacting system stability.
How do I fix CVE-2024-38549?
To fix CVE-2024-38549, upgrade your Linux kernel to versions 5.10.223-1, 6.1.123-1, or later patched versions.
Which versions of the Linux kernel are affected by CVE-2024-38549?
CVE-2024-38549 affects Linux kernel versions from 4.7 to 4.19.316 and several others up to 6.9.3.
What is the nature of the vulnerability in CVE-2024-38549?
CVE-2024-38549 pertains to a lack of size check in the mtk_drm_gem_init function, which can lead to kernel crashes.
Are there any upstream fixes for CVE-2024-38549?
Yes, upstream fixes for CVE-2024-38549 have been released in the latest kernel versions and can be applied to affected installations.