LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38543: drm/tegra: nvdec: Fix dma_alloc_coherent error check

In the Linux kernel, the following vulnerability has been resolved: drm/tegra: nvdec: Fix dma_alloc_coherent error check Check for NULL return value with dma_alloc_coherent, in line with Robin's fix for vic.c in 'drm/tegra: vic: Fix DMA API misuse'.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in the Tegra NVDEC graphics/video driver. The driver mishandled a failed DMA memory allocation check, which could lead to unsafe kernel behavior if allocation fails. The provided sources do not include a CVSS score, proven impact, or active exploitation evidence.

Executive priority

Treat as targeted kernel maintenance unless your fleet includes Tegra-based Linux devices. There is no active exploitation evidence in the supplied sources, but kernel flaws can carry operational risk and should be patched through normal vulnerability management channels.

Technical view

The issue is in drm/tegra nvdec: dma_alloc_coherent returns NULL on failure, and the kernel fix changes the error check accordingly. Exposure appears limited to affected Linux kernel builds with the Tegra NVDEC driver path present and relevant hardware or configuration.

Likely exposure

Most exposure is likely on Linux systems using NVIDIA Tegra SoC graphics/video decode support. Generic Linux servers without Tegra NVDEC support are less likely exposed. The source bundle lists affected kernel versions but does not provide distribution-by-distribution package status except a Debian LTS reference.

Exploitation context

The bundle does not show KEV listing, public exploitation, exploit maturity, or remote attack evidence. Based only on the provided description, this appears more like a local kernel reliability or denial-of-service class issue than an internet-facing vulnerability, but impact is not formally scored.

Researcher notes

Key evidence is limited to the CVE record and upstream stable commits. The root issue is a NULL return check for dma_alloc_coherent in the Tegra NVDEC driver. No CVSS, CWE, exploit details, or complete distribution impact matrix is provided.

Mitigation direction

  • Update affected Linux kernels to vendor-provided fixed builds.
  • Review the referenced stable kernel commits for the applicable maintained branch.
  • Check Debian LTS guidance if running Debian LTS kernels.
  • Prioritize systems using Tegra NVDEC or related DRM driver support.

Validation and detection

  • Inventory Linux kernel versions against the affected versions in the CVE record.
  • Confirm whether Tegra NVDEC DRM support is present or enabled.
  • Check distribution advisories for patched kernel package versions.
  • Verify deployed kernels include the referenced stable fix commits.
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-38543 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

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

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux46f226c93d35b936aeec6eb31da932dc2e86f413, 46f226c93d35b936aeec6eb31da932dc2e86f413, 46f226c93d35b936aeec6eb31da932dc2e86f413, 46f226c93d35b936aeec6eb31da932dc2e86f413, 46f226c93d35b936aeec6eb31da932dc2e86f413unaffected
LinuxLinux5.17, 0, 6.1.146, 6.6.99, 6.12.39, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

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