LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36779: i2c: stm32f7: fix reference leak when pm_runtime_get_sync fails

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

This is a Linux kernel defect in the STM32F7 I2C driver. A failed power-management resume call can leave a reference count unbalanced. The available sources do not describe remote exploitation, privilege escalation, data theft, or business impact, so urgency depends on whether affected embedded Linux devices use this driver.

Executive priority

Handle through normal kernel and firmware maintenance unless you operate STM32-based embedded Linux products at scale. The business urgency is not well established from the sources because severity, exploitability, and real-world abuse evidence are absent.

Technical view

The kernel fix replaces pm_runtime_get_sync with pm_runtime_resume_and_get in stm32f7 I2C functions because pm_runtime_get_sync increments the PM usage counter even on failure. Missing cleanup can cause a runtime power-management reference leak. Stable kernel commits are cited as fixes, but no CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions and the stm32f7 I2C driver path, especially embedded or STM32-based devices. Conventional Linux servers are less likely to be relevant unless this driver is built and used. The source bundle does not prove broad product exposure.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not describe an attack vector or required privileges. Treat this as an operational kernel reliability issue unless vendor guidance or later evidence says otherwise.

Researcher notes

Evidence is limited to the CVE text and Linux stable commit references. The affected version data appears sparse and repetitive in the bundle. There is no CVSS, CWE, KEV listing, exploit status, or detailed impact statement, so avoid stronger claims without vendor confirmation.

Mitigation direction

  • Upgrade to a kernel or vendor firmware containing the cited stable fixes.
  • Ask device vendors whether their kernels include an equivalent backport.
  • Prioritize embedded Linux assets using STM32F7 I2C hardware or driver support.
  • Avoid ad hoc driver disablement unless vendor guidance confirms operational safety.

Validation and detection

  • Inventory Linux kernel versions on embedded and appliance fleets.
  • Check kernel configuration and hardware for stm32f7 I2C driver use.
  • Confirm the cited commits or equivalent backports are present.
  • Review vendor advisories for device-specific affected and fixed builds.
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-36779 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
LinuxLinuxea6dd25deeb5b797a145be7f860e3085e7d104c3, ea6dd25deeb5b797a145be7f860e3085e7d104c3, ea6dd25deeb5b797a145be7f860e3085e7d104c3, ea6dd25deeb5b797a145be7f860e3085e7d104c3unaffected
LinuxLinux5.6, 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.