CVE-2026-52965

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 19, 2026
No patch confirmed yet.
generic

drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b2ed01e7ad3de80333e9b962a44024b094bc0b2b
generic

drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0124a09e3e5f5f6080efe9663b27af27933f8382

Vendor Advisories for CVE-2026-52965(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 16× in last 7d / 96× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 13:45 UTCEG score recompute
  5. 2026-08-24 13:45 UTCVendor advisory
  6. 2026-08-24 13:45 UTCGHSA enrichment
  7. 2026-08-23 12:19 UTCVendor advisory
  8. 2026-08-23 12:18 UTCGHSA enrichment
  9. 2026-08-22 13:09 UTCEG score recompute
  10. 2026-08-22 13:09 UTCVendor advisory
  11. 2026-08-22 13:09 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 06:42 UTCEG score recompute
  14. 2026-08-21 06:42 UTCVendor advisory
  15. 2026-08-21 06:42 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 07:32 UTCEG score recompute
  18. 2026-08-20 07:32 UTCVendor advisory
  19. 2026-08-20 07:32 UTCGHSA enrichment
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 02:15 UTCVendor advisory
  22. 2026-08-19 02:15 UTCGHSA enrichment
  23. 2026-08-17 15:19 UTCEG score recompute
  24. 2026-08-17 15:19 UTCVendor advisory
  25. 2026-08-17 15:19 UTCGHSA enrichment
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 16:10 UTCEG score recompute
  3. 2026-08-16 16:10 UTCVendor advisory
  4. 2026-08-16 16:10 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 17:01 UTCEG score recompute
  8. 2026-08-15 17:01 UTCVendor advisory
  9. 2026-08-15 17:01 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 17:52 UTCEG score recompute
  12. 2026-08-14 17:52 UTCVendor advisory
  13. 2026-08-14 17:52 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 18:37 UTCVendor advisory
  16. 2026-08-13 18:37 UTCGHSA enrichment
  17. 2026-08-12 18:06 UTCEG score recompute
  18. 2026-08-12 18:06 UTCVendor advisory
  19. 2026-08-12 18:06 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 18:56 UTCEG score recompute
  22. 2026-08-11 18:56 UTCVendor advisory
  23. 2026-08-11 18:56 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 19:47 UTCVendor advisory
  26. 2026-08-10 19:47 UTCGHSA enrichment
  27. 2026-08-09 20:37 UTCEG score recompute
  28. 2026-08-09 20:37 UTCVendor advisory
  29. 2026-08-09 20:37 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-08 21:28 UTCEG score recompute
  32. 2026-08-08 21:28 UTCVendor advisory
  33. 2026-08-08 21:28 UTCGHSA enrichment
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-07 22:18 UTCEG score recompute
  36. 2026-08-07 22:18 UTCVendor advisory
  37. 2026-08-07 22:18 UTCGHSA enrichment
  38. 2026-08-06 23:10 UTCEG score recompute
  39. 2026-08-06 23:10 UTCVendor advisory
  40. 2026-08-06 23:10 UTCGHSA enrichment
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-05 23:07 UTCEG score recompute
  43. 2026-08-05 23:07 UTCVendor advisory
  44. 2026-08-05 23:07 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 23:58 UTCEG score recompute
  47. 2026-08-04 23:58 UTCVendor advisory
  48. 2026-08-04 23:58 UTCGHSA enrichment
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-04 00:49 UTCEG score recompute
  52. 2026-08-04 00:49 UTCVendor advisory
  53. 2026-08-04 00:49 UTCGHSA enrichment
  54. 2026-08-03 10:36 UTCEPSS rescore
  55. 2026-08-03 01:40 UTCVendor advisory
  56. 2026-08-03 01:40 UTCGHSA enrichment
  57. 2026-08-02 02:31 UTCEG score recompute
  58. 2026-08-02 02:31 UTCVendor advisory
  59. 2026-08-02 02:31 UTCGHSA enrichment
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-08-01 03:21 UTCGHSA enrichment
  63. 2026-07-31 03:31 UTCEG score recompute
  64. 2026-07-31 03:31 UTCVendor advisory
  65. 2026-07-31 03:31 UTCGHSA enrichment
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 02:21 UTCEG score recompute
  68. 2026-07-30 02:21 UTCGHSA enrichment
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-29 00:59 UTCEG score recompute
  71. 2026-07-29 00:59 UTCGHSA enrichment
  72. 2026-07-28 15:37 UTCEPSS rescore
  73. 2026-07-27 17:40 UTCGHSA enrichment
  74. 2026-07-26 15:41 UTCEG score recompute
  75. 2026-07-26 15:41 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-52965?
CVE-2026-52965 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttmboswapout() infinite LRU walk on swapout failure When ttmttswapout() fails, the current code calls ttmresourceaddbulkmove() followed by ttmresourcemovetolru_tail() to restore the resource's bulk_move membership.…
When was CVE-2026-52965 disclosed?
CVE-2026-52965 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52965 actively exploited?
CVE-2026-52965 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-52965?
CVE-2026-52965 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52965?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52965, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52965

Explore →

Is Your Infrastructure Affected by CVE-2026-52965?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.