Skip to content
Fencer Vulns
medium 5.5

CVE-2020-36783 json

i2c: img-scb: fix reference leak when pm_runtime_get_sync fails

published 2024-02-28 2 y ago modified 2026-06-17 4 mo ago also EUVD-2020-24224

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 5.4.119, 5.10.37, 5.11.21, 5.12.4, 5.13
  • linux Debian 14, Debian 13, Debian 12 5.10.38-1

debian advisories DEBIAN-CVE-2020-36783

  • linux Ubuntu 20.04 LTS 5.4.0-77.86
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1051.53
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1046.49
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1041.42
  • linux-azure Ubuntu 20.04 LTS 5.4.0-1051.53
  • linux-gkeop Ubuntu 20.04 LTS 5.4.0-1018.19
  • linux-raspi Ubuntu 20.04 LTS 5.4.0-1038.41
  • linux-oracle Ubuntu 20.04 LTS 5.4.0-1048.52

ubuntu advisories UBUNTU-CVE-2020-36783

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-64kb SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS, Enterprise Storage 7.1 5.3.18-150300.59.158.1
  • kernel-syms SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.158.1
  • kernel-source SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.158.1
  • kernel-default SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +5 more 5.3.18-150300.59.158.1
  • kernel-preempt SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.158.1
  • kernel-obs-build SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.158.1
  • kernel-default-base SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +3 more 5.3.18-150300.59.158.1.150300.18.92.5
  • kernel-rt SLE Micro 5.2, SLE Micro 5.1 5.3.18-150300.166.1

suse advisories SUSE-SU-2024:1489-1SUSE-SU-2024:1465-1SUSE-SU-2024:1454-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-36783 updated cvss 4.4

kernel: i2c: img-scb: fix reference leak when pm_runtime_get_sync fails

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.