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(9)

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 (140 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 183 total refreshes for this CVE.

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