LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37765: drm/nouveau: prime: fix ttm_bo_delayed_delete oops

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: prime: fix ttm_bo_delayed_delete oops Fix an oops in ttm_bo_delayed_delete which results from dererencing a dangling pointer: Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b7b: 0000 [#1] PREEMPT SMP CPU: 4 UID: 0 PID: 1082 Comm: kworker/u65:2 Not tainted 6.14.0-rc4-00267-g505460b44513-dirty #216 Hardware name: LENOVO 82N6/LNVNB161216, BIOS GKCN65WW 01/16/2024 Workqueue: ttm ttm_bo_delayed_delete [ttm] RIP: 0010:dma_resv_iter_first_unlocked+0x55/0x290 Code: 31 f6 48 c7 c7 00 2b fa aa e8 97 bd 52 ff e8 a2 c1 53 00 5a 85 c0 74 48 e9 88 01 00 00 4c 89 63 20 4d 85 e4 0f 84 30 01 00 00 <41> 8b 44 24 10 c6 43 2c 01 48 89 df 89 43 28 e8 97 fd ff ff 4c 8b RSP: 0018:ffffbf9383473d60 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffffbf9383473d88 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffbf9383473d78 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 6b6b6b6b6b6b6b6b R13: ffffa003bbf78580 R14: ffffa003a6728040 R15: 00000000000383cc FS: 0000000000000000(0000) GS:ffffa00991c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000758348024dd0 CR3: 000000012c259000 CR4: 0000000000f50ef0 PKRU: 55555554 Call Trace: <TASK> ? __die_body.cold+0x19/0x26 ? die_addr+0x3d/0x70 ? exc_general_protection+0x159/0x460 ? asm_exc_general_protection+0x27/0x30 ? dma_resv_iter_first_unlocked+0x55/0x290 dma_resv_wait_timeout+0x56/0x100 ttm_bo_delayed_delete+0x69/0xb0 [ttm] process_one_work+0x217/0x5c0 worker_thread+0x1c8/0x3d0 ? apply_wqattrs_cleanup.part.0+0xc0/0xc0 kthread+0x10b/0x240 ? kthreads_online_cpu+0x140/0x140 ret_from_fork+0x40/0x70 ? kthreads_online_cpu+0x140/0x140 ret_from_fork_asm+0x11/0x20 </TASK> The cause of this is: - drm_prime_gem_destroy calls dma_buf_put(dma_buf) which releases the reference to the shared dma_buf. The reference count is 0, so the dma_buf is destroyed, which in turn decrements the corresponding amdgpu_bo reference count to 0, and the amdgpu_bo is destroyed - calling drm_gem_object_release then dma_resv_fini (which destroys the reservation object), then finally freeing the amdgpu_bo. - nouveau_bo obj->bo.base.resv is now a dangling pointer to the memory formerly allocated to the amdgpu_bo. - nouveau_gem_object_del calls ttm_bo_put(&nvbo->bo) which calls ttm_bo_release, which schedules ttm_bo_delayed_delete. - ttm_bo_delayed_delete runs and dereferences the dangling resv pointer, resulting in a general protection fault. Fix this by moving the drm_prime_gem_destroy call from nouveau_gem_object_del to nouveau_bo_del_ttm. This ensures that it will be run after ttm_bo_delayed_delete.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux graphics-kernel flaw can leave nouveau using freed memory during shared GPU-buffer cleanup. The documented result is a kernel protection fault, which can crash or destabilize a host. Its CVSS 7.8 assessment also indicates potentially severe confidentiality, integrity, and availability impact from a local, low-privileged attack path, although the supplied evidence demonstrates the crash rather than those broader outcomes.

Executive priority

Prioritize affected multi-GPU workstations, graphics servers, and other hosts permitting low-privileged local access. Treat remediation as high priority because successful triggering occurs in kernel context and the documented outcome is host instability. Internet exposure alone is not the deciding factor; local account access and use of the affected graphics path matter more.

Technical view

During DRM PRIME cleanup, dma_buf destruction can release an associated AMD GPU buffer and its reservation object. nouveau retains a dangling reservation pointer; delayed TTM buffer deletion later dereferences it, causing a use-after-free-style kernel fault. The upstream correction moves drm_prime_gem_destroy later in nouveau teardown, after ttm_bo_delayed_delete has completed.

Likely exposure

Exposure is most likely on affected Linux kernels where nouveau participates in DRM PRIME/TTM shared-buffer handling, particularly the documented nouveau and AMD GPU interaction. Systems not loading or using nouveau are less likely to reach this path. The supplied version data is insufficiently structured to determine exact distribution-package boundaries, so vendor-specific verification is required.

Exploitation context

The CVSS vector describes local access, low complexity, low privileges, and no user interaction. The supplied record does not show CISA KEV inclusion or cite active exploitation, a public exploit, or remote reachability. Absence from KEV does not prove exploitation has never occurred.

Researcher notes

The supplied trace supports a dangling dma_resv pointer after dma_buf_put releases the AMD buffer, followed by dereference from delayed TTM deletion. The fix is an object-lifetime ordering change, not input filtering. Researchers should distinguish the reproduced general-protection fault from the CVSS-assessed confidentiality and integrity impacts, which are not independently demonstrated in this bundle.

Mitigation direction

  • Install a vendor kernel containing the applicable upstream stable fix for CVE-2025-37765.
  • Review the cited Debian LTS advisories where those distributions and releases apply.
  • If patching is delayed, obtain vendor guidance for temporary nouveau or PRIME risk reduction.
  • Ensure systems boot the corrected kernel after the update is installed.

Validation and detection

  • Inventory running kernels and identify hosts using nouveau, TTM, DRM PRIME, or AMD GPU interoperability.
  • Map distribution kernel packages to vendor advisories and the applicable upstream stable fix commit.
  • Review kernel logs for faults involving ttm_bo_delayed_delete, dma_resv_wait_timeout, or nouveau object teardown.
  • After updating, confirm the corrected kernel is active and monitor for recurrence during normal graphics workloads.
Prepared
Confidence
medium
Sources
12

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-37765 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-37765Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262, 22b33e8ed0e38b8ddcf082e35580f2e67a3a0262unaffected
LinuxLinux3.5, 0, 5.4.293, 5.10.237, 5.15.181, 6.1.135, 6.6.88, 6.12.25, 6.14.4, 6.15affected
Weakness

CWE details

No CWE listed

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