CVE-2020-36787

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-02-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

media: aspeed: fix clock handling logic

Video engine uses eclk and vclk for its clock sources and its reset control is coupled with eclk so the current clock enabling sequence works like below.

Enable eclk De-assert Video Engine reset 10ms delay Enable vclk

It introduces improper reset on the Video Engine hardware and eventually the hardware generates unexpected DMA memory transfers that can corrupt memory region in random and sporadic patterns. This issue is observed very rarely on some specific AST2500 SoCs but it causes a critical kernel panic with making a various shape of signature so it's extremely hard to debug. Moreover, the issue is observed even when the video engine is not actively used because udevd turns on the video engine hardware for a short time to make a query in every boot.

To fix this issue, this commit changes the clock handling logic to make the reset de-assertion triggered after enabling both eclk and vclk. Also, it adds clk_unprepare call for a case when probe fails.

clk: ast2600: fix reset settings for eclk and vclk Video engine reset setting should be coupled with eclk to match it with the setting for previous Aspeed SoCs which is defined in clk-aspeed.c since all Aspeed SoCs are sharing a single video engine driver. Also, reset bit 6 is defined as 'Video Engine' reset in datasheet so it should be de-asserted when eclk is enabled. This commit fixes the setting.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

February 28, 2024

Last Modified

August 5, 2026

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2020-36787?
CVE-2020-36787 is a medium vulnerability published on February 28, 2024. In the Linux kernel, the following vulnerability has been resolved: media: aspeed: fix clock handling logic Video engine uses eclk and vclk for its clock sources and its reset control is coupled with eclk so the current clock enabling sequence works like below. Enable eclk De-assert Video Engine…
When was CVE-2020-36787 disclosed?
CVE-2020-36787 was first published in the National Vulnerability Database on February 28, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-36787 actively exploited?
CVE-2020-36787 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2020-36787?
CVE-2020-36787 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2020-36787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36787, 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

Explore the affected products and dependency analysis for CVE-2020-36787

Explore →

Is Your Infrastructure Affected by CVE-2020-36787?

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