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-26874drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip

Description

In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip It's possible that mtk_crtc->event is NULL in mtk_drm_crtc_finish_page_flip(). pending_needs_vblank value is set by mtk_crtc->event, but in mtk_drm_crtc_atomic_flush(), it's is not guarded by the same lock in mtk_drm_finish_page_flip(), thus a race condition happens. Consider the following case: CPU1 CPU2 step 1: mtk_drm_crtc_atomic_begin() mtk_crtc->event is not null, step 1: mtk_drm_crtc_atomic_flush: mtk_drm_crtc_update_config( !!mtk_crtc->event) step 2: mtk_crtc_ddp_irq -> mtk_drm_finish_page_flip: lock mtk_crtc->event set to null, pending_needs_vblank set to false unlock pending_needs_vblank set to true, step 2: mtk_crtc_ddp_irq -> mtk_drm_finish_page_flip called again, pending_needs_vblank is still true //null pointer Instead of guarding the entire mtk_drm_crtc_atomic_flush(), it's more efficient to just check if mtk_crtc->event is null before use.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years 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-26874, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 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 4.7.

Affected products

  • Linux · Linux

    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < accdac6b71d5a2b84040c3d2234f53a60edc398e
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < dfde84cc6c589f2a9f820f12426d97365670b731
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 4688be96d20ffa49d2186523ee84f475f316fd49
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 9beec711a17245b853d64488fd5b739031612340
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < d2bd30c710475b2e29288827d2c91f9e6e2b91d7
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < a3dd12b64ae8373a41a216a0b621df224210860a
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 9acee29a38b4d4b70f1f583e5ef9a245db4db710
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < 3fc88b246a2fc16014e374040fc15af1d3752535
    • affected 119f5173628aa7a0c3cf9db83460d40709e8241d – < c958e86e9cc1b48cac004a6e245154dfba8e163b
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 4.19.311 – ≤ 4.19.*
    • unaffected 5.4.273 – ≤ 5.4.*
    • unaffected 5.10.214 – ≤ 5.10.*
    • unaffected 5.15.153 – ≤ 5.15.*
    • unaffected 6.1.83 – ≤ 6.1.*
    • unaffected 6.6.23 – ≤ 6.6.*
    • unaffected 6.7.11 – ≤ 6.7.*
    • unaffected 6.8.2 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .