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-2025-38467drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling

Description

In the Linux kernel, the following vulnerability has been resolved: drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling If there's support for another console device (such as a TTY serial), the kernel occasionally panics during boot. The panic message and a relevant snippet of the call stack is as follows: Unable to handle kernel NULL pointer dereference at virtual address 000000000000000 Call trace: drm_crtc_handle_vblank+0x10/0x30 (P) decon_irq_handler+0x88/0xb4 [...] Otherwise, the panics don't happen. This indicates that it's some sort of race condition. Add a check to validate if the drm device can handle vblanks before calling drm_crtc_handle_vblank() to avoid this.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 10 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-2025-38467, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.20% · top 91% of all CVEs (14 Nov 2026)
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 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < b4e72c0bf878f02faa00a7dc7c9ffc4ff7c116a7
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < a2130463fc9451005660b0eda7b61d5f746f7d74
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < 87825fbd1e176cd5b896940f3959e7c9a916945d
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < a40a35166f7e4f6dcd4b087d620c8228922dcb0a
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < 391e5ea5b877230b844c9bd8bbcd91b681b1ce2d
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < e9d9b25f376737b81f06de9c5aa422b488f47184
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < 996740652e620ef8ee1e5c65832cf2ffa498577d
    • affected 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 – < b846350aa272de99bf6fecfa6b08e64ebfb13173
  • Linux · Linux

    • affected 4.0
    • unaffected < 4.0
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.189 – ≤ 5.15.*
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.99 – ≤ 6.6.*
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .