LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71083: drm/ttm: Avoid NULL pointer deref for evicted BOs

In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Avoid NULL pointer deref for evicted BOs It is possible for a BO to exist that is not currently associated with a resource, e.g. because it has been evicted. When devcoredump tries to read the contents of all BOs for dumping, we need to expect this as well -- in this case, ENODATA is recorded instead of the buffer contents.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can trigger a NULL pointer dereference while collecting GPU buffer-object data for a device core dump. The source indicates the corrected behavior records ENODATA when an evicted buffer has no backing resource. Business risk is currently hard to rank because no CVSS, CWE, impact rating, or exploitation evidence is provided.

Executive priority

Prioritize through normal kernel patch management unless systems show graphics-related kernel crashes or availability sensitivity is high. The issue is in kernel code, but public evidence does not currently support emergency handling or active-exploitation claims.

Technical view

The flaw is in drm/ttm devcoredump handling. A buffer object may be evicted and lack an associated resource, but dump collection still tried to read all BO contents. The stable fixes make the code tolerate resource-less BOs and record ENODATA instead of dereferencing NULL.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with DRM/TTM graphics memory management code present. The bundle lists Linux kernel versions including 4.14, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, and 6.19 as affected.

Exploitation context

No active exploitation is indicated. The CVE is not marked KEV, and the supplied sources do not describe public exploit use, attacker prerequisites, or a reliable trigger path. Treat this as a kernel stability and availability concern until vendor advisories clarify impact.

Researcher notes

The available record is sparse: no CVSS, CWE, exploitability assessment, or detailed affected-driver matrix is supplied. The root condition is a resource-less evicted BO encountered during devcoredump enumeration. Researchers should avoid over-scoping beyond DRM/TTM Linux kernel exposure.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Use distribution vendor advisories to map fixed package versions.
  • Prioritize systems using GPU drivers that rely on DRM/TTM paths.
  • Do not assume workaround availability without vendor guidance.
  • Schedule reboot validation after kernel package updates.

Validation and detection

  • Inventory running Linux kernel versions across affected systems.
  • Compare deployed kernels with vendor-fixed versions or referenced stable commits.
  • Review kernel crash logs for DRM, TTM, devcoredump, or NULL dereference messages.
  • Confirm updated kernels preserve expected graphics and dump behavior.
  • Track CVE record updates for severity or affected-version corrections.
Prepared
Confidence
medium
Sources
8

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-2025-71083 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
1ADP providers
7Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux09ac4fcb3f255e9225967c75f5893325c116cdbe, 09ac4fcb3f255e9225967c75f5893325c116cdbe, 09ac4fcb3f255e9225967c75f5893325c116cdbe, 09ac4fcb3f255e9225967c75f5893325c116cdbe, 09ac4fcb3f255e9225967c75f5893325c116cdbe, 09ac4fcb3f255e9225967c75f5893325c116cdbeunaffected
LinuxLinux4.14, 0, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

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