LiveActive security incident?Get immediate response
CVE Record

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

In the Linux kernel, the following vulnerability has been resolved: i2c: imx: fix reference leak when pm_runtime_get_sync fails In i2c_imx_xfer() and i2c_imx_remove(), the pm reference count is not expected to be incremented on return. However, pm_runtime_get_sync will increment 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

This is a Linux kernel driver bug in the i.MX I2C code. When a power-management resume call fails, the driver can leave a runtime power reference count unbalanced. The source bundle does not show remote code execution, privilege escalation, CVSS scoring, or active exploitation.

Executive priority

Treat as targeted platform hygiene, not an emergency, unless your fleet includes i.MX-based Linux devices. Severity and exploitation evidence are not provided, so remediation should follow normal kernel maintenance unless vendor guidance raises urgency.

Technical view

The issue is in i2c_imx_xfer() and i2c_imx_remove(). pm_runtime_get_sync can increment the runtime PM usage counter even on failure; missing cleanup causes a reference leak. The resolved change replaces it with pm_runtime_resume_and_get to keep the counter balanced.

Likely exposure

Exposure is most likely limited to Linux systems using the i.MX I2C driver on affected kernel versions or downstream kernels carrying the vulnerable code. Generic Linux servers without this hardware or driver path are less likely to be exposed.

Exploitation context

The provided sources do not identify active exploitation, KEV listing, exploit availability, attack prerequisites, or attacker impact. The described failure mode is a kernel driver reference leak tied to runtime power-management error handling.

Researcher notes

Evidence is narrow: the bundle describes a resolved runtime PM reference leak and lists kernel stable commits, but provides no CVSS, CWE, exploit status, or detailed affected-version ranges beyond the supplied Linux entries.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize Linux systems using NXP/Freescale i.MX I2C hardware.
  • Check distribution advisories for backported fixes in supported kernels.
  • Track kernel or vendor guidance if fixed packages are unavailable.

Validation and detection

  • Inventory systems running Linux on i.MX-based platforms.
  • Check whether the i2c-imx driver is present and in use.
  • Compare running kernel builds against vendor fixed releases.
  • Review downstream kernel changelogs for the referenced stable commits.
Prepared
Confidence
medium
Sources
6

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-36781 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
5Source 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
LinuxLinux3a5ee18d2a32bda6b9a1260136f6805848e3839d, 3a5ee18d2a32bda6b9a1260136f6805848e3839d, 3a5ee18d2a32bda6b9a1260136f6805848e3839d, 3a5ee18d2a32bda6b9a1260136f6805848e3839dunaffected
LinuxLinux5.7, 0, 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.