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-40110drm/vmwgfx: Fix a null-ptr access in the cursor snooper

Description

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix a null-ptr access in the cursor snooper Check that the resource which is converted to a surface exists before trying to use the cursor snooper on it. vmw_cmd_res_check allows explicit invalid (SVGA3D_INVALID_ID) identifiers because some svga commands accept SVGA3D_INVALID_ID to mean "no surface", unfortunately functions that accept the actual surfaces as objects might (and in case of the cursor snooper, do not) be able to handle null objects. Make sure that we validate not only the identifier (via the vmw_cmd_res_check) but also check that the actual resource exists before trying to do something with it. Fixes unchecked null-ptr reference in the snooping code.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 6 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < 3332212e93d0f6e24f8fe79f975e077c4e68ca39
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < 86aae7053d2da3fdfde7b2e84d86e4af50490505
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < af9d88cbf0fce52f465978360542ef679713491f
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < 299cfb5a7deabdf9ecd30071755672af0aced5eb
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < 13c9e4ed125e19484234c960efe5ac9c55119523
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < b6fca0a07989f361ceda27cb2d09c555d4d4a964
    • affected c0951b797e7d0f2c6b0df2c0e18185c72d0cf1a1 – < 5ac2c0279053a2c5265d46903432fb26ae2d0da2
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.113 – ≤ 6.6.*
    • unaffected 6.12.54 – ≤ 6.12.*
    • unaffected 6.17.4 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .