# drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure

CVE record · `CVE-2026-52965`

- **Identifiers:** `CVE-2026-52965`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Jun 2026, 16:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `fc5d96670eb2540d2572a14351e82ffe45d5ac11 to before 060f8f3020516d71bc4d6159d4d0beef85606a74` (git)
  - affected: `fc5d96670eb2540d2572a14351e82ffe45d5ac11 to before 0124a09e3e5f5f6080efe9663b27af27933f8382` (git)
  - affected: `fc5d96670eb2540d2572a14351e82ffe45d5ac11 to before b2ed01e7ad3de80333e9b962a44024b094bc0b2b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.13`
  - unaffected: `before 6.13` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.10 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel DRM/TTM memory manager can enter an infinite loop in ttm_bo_swapout() when a swapout fails, affecting 6.13 and later versions before the fixes. The source gives few details on what an attacker would need to trigger it or what the loop causes beyond hanging the walk. Upgrade to 6.18.57 or later, 7.0.10 or later, or 7.1 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jun 2026, 16:28 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-52965)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-52965)

## Sources

- [CVE List: CVE-2026-52965](https://www.cve.org/CVERecord?id=CVE-2026-52965)
- [NVD: CVE-2026-52965](https://nvd.nist.gov/vuln/detail/CVE-2026-52965)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-52965>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-52965/>. Everything for agents: <https://agentprime.io/llms.txt>.
