CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2020-36787 – media: aspeed: fix clock handling logic
https://notcve.org/view.php?id=CVE-2020-36787
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. • https://git.kernel.org/stable/c/d2b4387f3bdf016e266d23cf657465f557721488 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 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2020-36786 – media: [next] staging: media: atomisp: fix memory leak of object flash
https://notcve.org/view.php?id=CVE-2020-36786
In the Linux kernel, the following vulnerability has been resolved: media: [next] staging: media: atomisp: fix memory leak of object flash In the case where the call to lm3554_platform_data_func returns an error there is a memory leak on the error return path of object flash. Fix this by adding an error return path that will free flash and rename labels fail2 to fail3 and fail1 to fail2. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: [siguiente] staging: media: atomisp: corrige la pérdida de memoria del flash del objeto En el caso de que la llamada a lm3554_platform_data_func devuelva un error, hay una pérdida de memoria en la ruta de retorno del error del destello del objeto. Solucione este problema agregando una ruta de retorno de error que liberará el flash y cambiará el nombre de las etiquetas de falla2 a falla3 y de falla1 a falla2. • https://git.kernel.org/stable/c/9289cdf399922a1bd801a8cd946a79581c00a380 https://git.kernel.org/stable/c/cc4cc2fb5aaf9adb83c02211eb13b16cfcb7ba64 https://git.kernel.org/stable/c/4f0f37d03cde8f4341df8454f9b40a67fda94a33 https://git.kernel.org/stable/c/27d2eab69f7da8e94e4751ac5c6d22d809275484 https://git.kernel.org/stable/c/6045b01dd0e3cd3759eafe7f290ed04c957500b1 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2020-36785 – media: atomisp: Fix use after free in atomisp_alloc_css_stat_bufs()
https://notcve.org/view.php?id=CVE-2020-36785
In the Linux kernel, the following vulnerability has been resolved: media: atomisp: Fix use after free in atomisp_alloc_css_stat_bufs() The "s3a_buf" is freed along with all the other items on the "asd->s3a_stats" list. It leads to a double free and a use after free. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: medios: atomisp: Corrige el use after free en atomisp_alloc_css_stat_bufs() El "s3a_buf" se libera junto con todos los demás elementos de la lista "asd->s3a_stats". Conduce a una doble gratuidad y un use after free. • https://git.kernel.org/stable/c/ad85094b293e40e7a2f831b0311a389d952ebd5e https://git.kernel.org/stable/c/d218c7a0284f6b92a7b82d2e19706e18663b4193 https://git.kernel.org/stable/c/801c1d505894008c888bc71d08d5cff5d87f8aba https://git.kernel.org/stable/c/8267ccd7b9df7ab682043507dd682fe0621cf045 https://git.kernel.org/stable/c/ba11bbf303fafb33989e95473e409f6ab412b18d •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2020-36784 – i2c: cadence: fix reference leak when pm_runtime_get_sync fails
https://notcve.org/view.php?id=CVE-2020-36784
In the Linux kernel, the following vulnerability has been resolved: i2c: cadence: fix reference leak when pm_runtime_get_sync fails The PM reference count is not expected to be incremented on return in functions cdns_i2c_master_xfer and cdns_reg_slave. However, pm_runtime_get_sync will increment pm usage counter even failed. Forgetting to putting operation will result in a reference leak here. Replace it with pm_runtime_resume_and_get to keep usage counter balanced. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: i2c: cadencia: corrige la fuga de referencia cuando falla pm_runtime_get_sync No se espera que el recuento de referencias de PM aumente al regresar en las funciones cdns_i2c_master_xfer y cdns_reg_slave. Sin embargo, pm_runtime_get_sync incrementará el contador de uso de pm incluso si falla. Olvidarse de poner en funcionamiento resultará en una fuga de referencia aquí. • https://git.kernel.org/stable/c/7fa32329ca03148fb2c07b4ef3247b8fc0488d6a https://git.kernel.org/stable/c/30410519328c94367e561fd878e5f0d3a0303585 https://git.kernel.org/stable/c/d57ff04e0ed6f3be1682ae861ead33f879225e07 https://git.kernel.org/stable/c/a45fc41beed8e0fe31864619c34aa00797fb60c1 https://git.kernel.org/stable/c/23ceb8462dc6f4b4decdb5536a7e5fc477cdf0b6 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2020-36783 – i2c: img-scb: fix reference leak when pm_runtime_get_sync fails
https://notcve.org/view.php?id=CVE-2020-36783
In the Linux kernel, the following vulnerability has been resolved: i2c: img-scb: fix reference leak when pm_runtime_get_sync fails The PM reference count is not expected to be incremented on return in functions img_i2c_xfer and img_i2c_init. However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here. Replace it with pm_runtime_resume_and_get to keep usage counter balanced. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: i2c: img-scb: corrige la fuga de referencia cuando falla pm_runtime_get_sync No se espera que el recuento de referencias de PM aumente al regresar en las funciones img_i2c_xfer e img_i2c_init. Sin embargo, pm_runtime_get_sync incrementará el recuento de referencias de PM incluso si falla. Olvidarse de poner en funcionamiento resultará en una fuga de referencia aquí. • https://git.kernel.org/stable/c/93222bd9b966105f43418fd336654ad10045783a https://git.kernel.org/stable/c/4734c4b1d9573c9d20bbc46cf37dde095ee011b8 https://git.kernel.org/stable/c/e80ae8bde41266d3b8bf012460b6593851766006 https://git.kernel.org/stable/c/96c4a03658d661666c360959aa80cdabfe2972ed https://git.kernel.org/stable/c/7ee35cde1e810ad6ca589980b9ec2b7b62946a5b https://git.kernel.org/stable/c/223125e37af8a641ea4a09747a6a52172fc4b903 •