LiveActive security incident?Get immediate response
CVE Record

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 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash affected systems that use the MediaTek DRM graphics driver when a local userspace program requests a zero-size graphics buffer. The reported impact is denial of service, not data theft or remote compromise. Public sources do not provide CVSS, CWE, or evidence of active exploitation.

Executive priority

Prioritize patching affected MediaTek-based Linux devices where local users, kiosk apps, browsers, containers with graphics access, or untrusted workloads can interact with the graphics stack. This is less urgent for non-MediaTek infrastructure or systems without local graphics exposure.

Technical view

The issue is in mtk_drm_gem_init within the MediaTek DRM GEM path. Before the fix, a zero-byte GEM/GBM buffer allocation could trigger a kernel panic. The kernel fix adds a zero-size check and returns EINVAL instead. Testing cited MT8188; broader exposure depends on affected kernel versions and MediaTek DRM driver use.

Likely exposure

Exposure is most likely on Linux systems using affected kernel builds with the MediaTek DRM graphics stack enabled. It appears local and hardware/driver-specific. Generic servers without MediaTek DRM/GPU usage are unlikely to be exposed based on the provided sources.

Exploitation context

The CVE is not in CISA KEV, and the source bundle cites no active exploitation. The described trigger requires userspace interaction with graphics buffer allocation and results in kernel panic. Treat this primarily as a local denial-of-service risk until better evidence appears.

Researcher notes

Evidence is limited to kernel resolution text, stable commit references, and a Debian LTS advisory. No CVSS, CWE, exploit status, or complete product matrix is provided. The strongest claim supported is local denial of service via kernel panic before the EINVAL fix.

Mitigation direction

  • Update to a kernel containing the referenced stable fix for CVE-2024-38549.
  • Apply relevant distribution kernel updates, including Debian LTS guidance where applicable.
  • Confirm vendor kernels have backported the zero-size GEM allocation check.
  • Reduce untrusted local application access on affected MediaTek graphics systems until patched.
  • For embedded fleets, request firmware or BSP updates from the device vendor.

Validation and detection

  • Inventory Linux hosts and devices using MediaTek DRM graphics drivers.
  • Map running kernel versions against the affected and fixed kernel branches.
  • Verify source or changelog includes the mtk_drm_gem_init zero-size check.
  • In staging, confirm invalid zero-size graphics allocations fail safely without kernel panic.
  • Track Debian or vendor advisories for package-level fixed versions.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38549 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241d, 119f5173628aa7a0c3cf9db83460d40709e8241dunaffected
LinuxLinux4.7, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.