CVE-2026-64100

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

August 11, 2026

Advisory Details (3)

Auto-updated Aug 11, 2026
Patch available.
Web page

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

https://git.kernel.org/stable/c/942968260e61d4a5d7552b20814b6277f9c553df
Web page

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

https://git.kernel.org/stable/c/928788566c79046f71a211fc32c115400be76402
Web page

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

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-01ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-01ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-01ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-01ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-01ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-01ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-01ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-01ubuntu

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 184 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64100?
CVE-2026-64100 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-64100 published?
The CVE record for CVE-2026-64100 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 11, 2026; the record at its source may have been updated since.
Is CVE-2026-64100 actively exploited?
CVE-2026-64100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-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?
A fix for CVE-2026-64100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64100 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs