CVE-2024-38549
drm/mediatek: Add 0 size check to mtk_drm_gem_obj
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add 0 size check to mtk_drm_gem_obj Add a check to mtk_drm_gem_init 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.7
References 9
git.kernel.org
- stable/c/79078880795478d551a05acc41f957700030d364
- stable/c/be34a1b351ea7faeb15dde8c44fe89de3980ae67
- stable/c/d17b75ee9c2e44d3a3682c4ea5ab713ea6073350
- stable/c/0e3b6f9123726858cac299e1654e3d20424cabe4
- stable/c/13562c2d48c9ee330de1077d00146742be368f05
- stable/c/af26ea99019caee1500bf7e60c861136c0bf8594
- stable/c/9489951e3ae505534c4013db4e76b1b5a3151ac7
- stable/c/fb4aabdb1b48c25d9e1ee28f89440fd2ce556405
- stable/c/1e4350095e8ab2577ee05f8c3b044e661b5af9a0