Answer in brief
CVE-2020-36787 records a High severity (CVSS 7.8) vulnerability in media: aspeed: fix clock handling logic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d2b4387f3bdf016e266d23cf657465f557721488 <1dc1d30ac101bb8335d9852de2107af60c2580e7 || >=d2b4387f3bdf016e266d23cf657465f557721488 <a59d01384c80a8a4392665802df57c3df20055f5 || >=d2b4387f3bdf016e266d23cf657465f557721488 <2964c37563e86cfdc439f217eb3c5a69adfdba6a || >=d2b4387f3bdf016e266d23cf657465f557721488 <75321dc8aebe3f30eff226028fe6da340fe0bf02 || >=d2b4387f3bdf016e266d23cf657465f557721488 <3536169f8531c2c5b153921dc7d1ac9fd570cda7 | 1dc1d30ac101bb8335d9852de2107af60c2580e7, a59d01384c80a8a4392665802df57c3df20055f5, 2964c37563e86cfdc439f217eb3c5a69adfdba6a, 75321dc8aebe3f30eff226028fe6da340fe0bf02, 3536169f8531c2c5b153921dc7d1ac9fd570cda7 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Feb 28, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.