CVE-2026-64100

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. 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/msm: Fix shrinker deadlock

With PROVE_LOCKING on an Snapdragon X1 and VM reclaim pressure, we see:

====================================================== WARNING: possible circular locking dependency detected 7.0.0-debug+ #43 Tainted: G W ------------------------------------------------------ kswapd0/82 is trying to acquire lock: ffff800080ec3870 (reservation_ww_class_acquire){+.+.}-{0:0}, at: msm_gem_shrinker_scan+0x17c/0x400 [msm]

but task is already holding lock: ffffc31709b263b8 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x88/0x988

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #2 (fs_reclaim){+.+.}-{0:0}: __lock_acquire+0x4d0/0xad0 lock_acquire.part.0+0xc4/0x248 lock_acquire+0x8c/0x248 fs_reclaim_acquire+0xd0/0xf0 dma_resv_lockdep+0x224/0x348 do_one_initcall+0x84/0x5d0 do_initcalls+0x194/0x1d8 kernel_init_freeable+0x128/0x180 kernel_init+0x2c/0x160 ret_from_fork+0x10/0x20

-> #1 (reservation_ww_class_mutex){+.+.}-{4:4}: __lock_acquire+0x4d0/0xad0 lock_acquire.part.0+0xc4/0x248 lock_acquire+0x8c/0x248 dma_resv_lockdep+0x1a8/0x348 do_one_initcall+0x84/0x5d0 do_initcalls+0x194/0x1d8 kernel_init_freeable+0x128/0x180 kernel_init+0x2c/0x160 ret_from_fork+0x10/0x20

-> #0 (reservation_ww_class_acquire){+.+.}-{0:0}: check_prev_add+0x114/0x790 validate_chain+0x594/0x6f0 __lock_acquire+0x4d0/0xad0 lock_acquire.part.0+0xc4/0x248 lock_acquire+0x8c/0x248 drm_gem_lru_scan+0x1ac/0x440 msm_gem_shrinker_scan+0x17c/0x400 [msm] do_shrink_slab+0x150/0x4a0 shrink_slab+0x144/0x460 shrink_one+0x9c/0x1b0 shrink_many+0x27c/0x5c0 shrink_node+0x344/0x550 balance_pgdat+0x2c0/0x988 kswapd+0x11c/0x318 kthread+0x10c/0x128 ret_from_fork+0x10/0x20

other info that might help us debug this: Chain exists of: reservation_ww_class_acquire --> reservation_ww_class_mutex --> fs_reclaim Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(fs_reclaim); lock(reservation_ww_class_mutex); lock(fs_reclaim); lock(reservation_ww_class_acquire);

* DEADLOCK * 1 lock held by kswapd0/82: #0: ffffc31709b263b8 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x88/0x988

stack backtrace: CPU: 4 UID: 0 PID: 82 Comm: kswapd0 Tainted: G W 7.0.0-debug+ #43 PREEMPT(full) Tainted: [W]=WARN Hardware name: LENOVO 21BX0016US/21BX0016US, BIOS N3HET94W (1.66 ) 09/15/2025 Call trace: show_stack+0x20/0x40 (C) dump_stack_lvl+0x9c/0xd0 dump_stack+0x18/0x30 print_circular_bug+0x114/0x120 check_noncircular+0x178/0x198 check_prev_add+0x114/0x790 validate_chain+0x594/0x6f0 __lock_acquire+0x4d0/0xad0 lock_acquire.part.0+0xc4/0x248 lock_acquire+0x8c/0x248 drm_gem_lru_scan+0x1ac/0x440 msm_gem_shrinker_scan+0x17c/0x400 [msm] do_shrink_slab+0x150/0x4a0 shrink_slab+0x144/0x460 shrink_one+0x9c/0x1b0 shrink_many+0x27c/0x5c0 shrink_node+0x344/0x550 balance_pgdat+0x2c0/0x988 kswapd+0x11c/0x318 kthread+0x10c/0x128 ret_from_fork+0x10/0x20

kswapd0 holding fs_reclaim calls the MSM shrinker, which calls dma_resv_lock. This in turn acquires fs_reclaim.

Fix this deadlock by using dma_resv_trylock() instead, dropping the subsequently unused passed wait-wound lock 'ticket'.

Patchwork: https://patchwork.freedesktop.org/patch/723564/ [rob: fixup compile errors, replace lockdep splat with somethin ---truncated---

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
1%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 11, 2026

Advisory Details (3)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

drm/msm: Fix shrinker deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/942968260e61d4a5d7552b20814b6277f9c553df
generic

drm/msm: Fix shrinker deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/928788566c79046f71a211fc32c115400be76402
generic

drm/msm: Fix shrinker deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3392291fc509d8ad6e4ad90f15b0a193f721cbc9

Vendor Advisories for CVE-2026-64100(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu

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 (141 versions)7.0.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 67× 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 147 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64100?
CVE-2026-64100 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix shrinker deadlock With PROVE_LOCKING on an Snapdragon X1 and VM reclaim pressure, we see: ====================================================== WARNING: possible circular locking dependency detected 7.0.0-debug+ #43…
When was CVE-2026-64100 disclosed?
CVE-2026-64100 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64100 actively exploited?
CVE-2026-64100 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 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64100?
CVE-2026-64100 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64100, 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-64100

Explore →

Is Your Infrastructure Affected by CVE-2026-64100?

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

Start Free Scan →Browse All CVEs