CVE-2020-36787

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.

Gravité et risque d'exploitation

CVE-2020-36787 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.23 %, ce qui la place devant 13.2 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=5.11.*, <1dc1d30ac101bb8335d9852de2107af60c2580e7, 0, <3536169f8531c2c5b153921dc7d1ac9fd570cda7, <=5.10.*, 5.10.37, 5.0, 5.11.21, <a59d01384c80a8a4392665802df57c3df20055f5, <=5.4.*, 5.13, <5.0, <=5.12.*, 5.12.4, 5.4.119, <75321dc8aebe3f30eff226028fe6da340fe0bf02, <=*, d2b4387f3bdf016e266d23cf657465f557721488, <2964c37563e86cfdc439f217eb3c5a69adfdba6a) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/1dc1d30ac101bb8335d9852de2107af60c2580e7
• https://git.kernel.org/stable/c/a59d01384c80a8a4392665802df57c3df20055f5
• https://git.kernel.org/stable/c/2964c37563e86cfdc439f217eb3c5a69adfdba6a
• https://git.kernel.org/stable/c/75321dc8aebe3f30eff226028fe6da340fe0bf02
• https://git.kernel.org/stable/c/3536169f8531c2c5b153921dc7d1ac9fd570cda7