dbcve.org
Linux KernelOperating system · Linux

CVE-2026-52965

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's TTM (Translation Table Manager) subsystem, a logic bug in ttm_bo_swapout() causes an infinite loop when swapout fails. After ttm_tt_swapout() fails, the code restores the resource's bulk_move membership by calling ttm_resource_move_to_lru_tail(), which places the resource in front of the walk cursor's hitch node. This causes list_for_each_entry_continue() to find the same resource repeatedly, resulting in an infinite LRU walk that hangs the system.

MitigationThis is a kernel bug requiring a code fix. The fix involves modifying the failure path in ttm_bo_swapout() to defer del_bulk_move to the success path only, and adding a new helper function ttm_resource_del_bulk_move_unevictable() to handle the swapped state correctly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.13, < 7.0.10= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run `uname -r` or `cat /proc/version` to identify the running Linux kernel version
    Affected if The kernel version is >= 6.13 and < 7.0.10, or exactly 7.1
  2. Verify TTM subsystem is active
    Check if TTM-using GPU drivers are loaded: run `lsmod | grep -E 'i915|amdgpu|radeon|vmwgfx|nouveau'` or check if /sys/module/ttm/ exists
    Affected if A TTM-based GPU driver (i915, amdgpu, radeon, vmwgfx, nouveau) is loaded or built into the kernel
  3. Confirm GPU memory pressure scenarios
    Monitor dmesg for TTM swapout activity or check GPU memory usage via /sys/class/drm/card*/device/mem_info_vram_used while running graphics workloads
    Affected if Swapout operations are being attempted on the system, which can trigger the infinite loop path when swapout fails

The system is affected if running a vulnerable kernel version (>= 6.13, < 7.0.10 or = 7.1) with TTM-based GPU drivers loaded and experiencing GPU memory swapout failures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.10 or later
Fixed in 7.0.10
Interim mitigation

This is a kernel bug requiring a code fix. The fix involves modifying the failure path in ttm_bo_swapout() to defer del_bulk_move to the success path only, and adding a new helper function ttm_resource_del_bulk_move_unevictable() to handle the swapped state correctly.

Recommended fix High confidence

Linux Kernel >= 7.0.10

  1. Identify the current kernel version using `uname -r`
  2. Check if the version is affected: >= 6.13 and < 7.0.10, or exactly 7.1
  3. If affected, upgrade to Linux kernel version 7.0.10 or later using your distribution's package manager
  4. For example, on Debian/Ubuntu: `apt-get update && apt-get install linux-image-<version>`
  5. On RHEL/CentOS: `yum update kernel`
  6. On Fedora: `dnf update kernel`
  7. Reboot into the new kernel
  8. Verify the fix is applied by checking the kernel version and confirming the vulnerability is resolved
Caveat Upgrading kernel major versions may require updating kernel modules or drivers; ensure compatible GPU/drm drivers are available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52965 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data