Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-38549drm/mediatek: Add 0 size check to mtk_drm_gem_obj

Description

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

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38549, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 79078880795478d551a05acc41f957700030d364
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < be34a1b351ea7faeb15dde8c44fe89de3980ae67
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < d17b75ee9c2e44d3a3682c4ea5ab713ea6073350
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 0e3b6f9123726858cac299e1654e3d20424cabe4
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 13562c2d48c9ee330de1077d00146742be368f05
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < af26ea99019caee1500bf7e60c861136c0bf8594
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 9489951e3ae505534c4013db4e76b1b5a3151ac7
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < fb4aabdb1b48c25d9e1ee28f89440fd2ce556405
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 1e4350095e8ab2577ee05f8c3b044e661b5af9a0
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.278 – ≤ 5.4.*
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38549 badge
[![CVE-2024-38549](https://cveledger.app/badge/CVE-2024-38549.svg)](https://cveledger.app/cve/CVE-2024-38549)

Record last updated .