Linux Kernel up to 5.4.118/5.10.36/5.11.20/5.12.3 img-scb pm_runtime_get_sync memory leak

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.4.118/5.10.36/5.11.20/5.12.3. It has been declared as problematic. This vulnerability affects the function pm_runtime_get_sync of the component img-scb. Executing a manipulation can lead to memory leak. This vulnerability is handled as CVE-2020-36783. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 5.4.118/5.10.36/5.11.20/5.12.3 (Operating System). This vulnerability affects the function pm_runtime_get_sync of the component img-scb. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:

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.

The weakness was released 02/28/2024. The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2020-36783 since 02/26/2024. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 247012 (Linux Distros Unpatched Vulnerability : CVE-2020-36783), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.119, 5.10.37, 5.11.21, 5.12.4 or 5.13 eliminates this vulnerability. Applying the patch 4734c4b1d957/e80ae8bde412/96c4a03658d6/7ee35cde1e81/223125e37af8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (247012). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.4.118
• 5.10.0
• 5.10.1
• 5.10.2
• 5.10.3
• 5.10.4
• 5.10.5
• 5.10.6
• 5.10.7
• 5.10.8
• 5.10.9
• 5.10.10
• 5.10.11
• 5.10.12
• 5.10.13
• 5.10.14
• 5.10.15
• 5.10.16
• 5.10.17
• 5.10.18
• 5.10.19
• 5.10.20
• 5.10.21
• 5.10.22
• 5.10.23
• 5.10.24
• 5.10.25
• 5.10.26
• 5.10.27
• 5.10.28
• 5.10.29
• 5.10.30
• 5.10.31
• 5.10.32
• 5.10.33
• 5.10.34
• 5.10.35
• 5.10.36
• 5.11.0
• 5.11.1
• 5.11.2
• 5.11.3
• 5.11.4
• 5.11.5
• 5.11.6
• 5.11.7
• 5.11.8
• 5.11.9
• 5.11.10
• 5.11.11
• 5.11.12
• 5.11.13
• 5.11.14
• 5.11.15
• 5.11.16
• 5.11.17
• 5.11.18
• 5.11.19
• 5.11.20
• 5.12.0
• 5.12.1
• 5.12.2
• 5.12.3

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion