Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-36787

media: aspeed: fix clock handling logic

High7.8EPSS 0.23%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-36787, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected d2b4387f3bdf016e266d23cf657465f557721488 – < 1dc1d30ac101bb8335d9852de2107af60c2580e7
    • affected d2b4387f3bdf016e266d23cf657465f557721488 – < a59d01384c80a8a4392665802df57c3df20055f5
    • affected d2b4387f3bdf016e266d23cf657465f557721488 – < 2964c37563e86cfdc439f217eb3c5a69adfdba6a
    • affected d2b4387f3bdf016e266d23cf657465f557721488 – < 75321dc8aebe3f30eff226028fe6da340fe0bf02
    • affected d2b4387f3bdf016e266d23cf657465f557721488 – < 3536169f8531c2c5b153921dc7d1ac9fd570cda7
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.119 – ≤ 5.4.*
    • unaffected 5.10.37 – ≤ 5.10.*
    • unaffected 5.11.21 – ≤ 5.11.*
    • unaffected 5.12.4 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-36787 badge
[![CVE-2020-36787](https://trackcve.app/badge/CVE-2020-36787.svg)](https://trackcve.app/cve/CVE-2020-36787)

Record last updated .