LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36782: i2c: imx-lpi2c: fix reference leak when pm_runtime_get_sync fails

In the Linux kernel, the following vulnerability has been resolved: i2c: imx-lpi2c: fix reference leak when pm_runtime_get_sync fails The PM reference count is not expected to be incremented on return in lpi2c_imx_master_enable. 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-36782 is a Linux kernel bug in the i.MX LPI2C driver. When a power-management resume call fails, the driver can leak a runtime power reference. The sources do not provide CVSS, CWE, business impact, or exploitation evidence.

Executive priority

Treat this as a routine kernel hygiene item unless affected i.MX-based systems are operationally important. There is no cited active exploitation or severity score, but unresolved driver resource leaks can affect reliability in embedded or appliance environments.

Technical view

The issue is in lpi2c_imx_master_enable. pm_runtime_get_sync increments the PM usage counter even on failure, and the error path did not release it. The kernel fix replaces it with pm_runtime_resume_and_get so the runtime PM counter remains balanced.

Likely exposure

Exposure appears limited to Linux kernels with the imx-lpi2c I2C driver present and relevant i.MX LPI2C hardware or configurations. The source bundle lists affected Linux kernel version markers including 4.16, 5.4.119, 5.10.37, 5.11.21, 5.12.4, and 5.13, but does not give complete range semantics.

Exploitation context

The bundle says this CVE is not in KEV and provides no public evidence of active exploitation. The described failure mode is a reference leak in a driver error path, not a demonstrated remote exploit or privilege escalation.

Researcher notes

The evidence supports a narrow driver-level runtime PM reference leak. Impact details are sparse: no CVSS, CWE, exploitability analysis, or precise affected-version ranges are included. Researchers should map vendor kernel trees and distro backports against the stable commit references.

Mitigation direction

  • Update to a kernel containing the listed stable fixes.
  • Check Linux distribution advisories for backported kernel packages.
  • Prioritize systems using i.MX LPI2C hardware or the imx-lpi2c driver.
  • If unused, consider disabling the driver through supported platform configuration.

Validation and detection

  • Inventory kernel versions on Linux systems using i.MX platforms.
  • Confirm whether the imx-lpi2c driver is built, loaded, or required.
  • Verify the kernel includes one of the referenced stable commits or a distro backport.
  • Review logs for recurring I2C or runtime power-management failures.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-36782 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux13d6eb20fc79a1e606307256dad4098375539a09, 13d6eb20fc79a1e606307256dad4098375539a09, 13d6eb20fc79a1e606307256dad4098375539a09, 13d6eb20fc79a1e606307256dad4098375539a09, 13d6eb20fc79a1e606307256dad4098375539a09unaffected
LinuxLinux4.16, 0, 5.4.119, 5.10.37, 5.11.21, 5.12.4, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.