Memory leak in Tensorflow
Impact
If a user passes a list of strings to dlpack.to_dlpack there is a memory leak following an expected validation failure:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L100-L104
The allocated memory is from https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L256
The issue occurs because the status argument during validation failures is not properly checked:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267
Since each of the above methods can return an error status, the status value must be checked before continuing.
Patches
We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.
We recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been discovered during variant analysis of GHSA-rjjg-hgv6-h69v.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | tensorflow | >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 | 2.2.1, 2.3.1 |
| Python (PyPI) | tensorflow-cpu | >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 | 2.2.1, 2.3.1 |
| Python (PyPI) | tensorflow-gpu | >= 2.2.0, < 2.2.1, >= 2.3.0, < 2.3.1 | 2.2.1, 2.3.1 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
- https://nvd.nist.gov/vuln/detail/CVE-2020-15192
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-272.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-307.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-115.yaml
- https://github.com/tensorflow/tensorflow
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L- Weakness (CWE)
CWE-20- Platform
- Python (PyPI)
- Package
tensorflow, tensorflow-cpu, tensorflow-gpu- Disclosed
- 25.09.2020
- Updated
- 11.10.2026 13:19
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2020-115 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2020-272 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2020-307 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-8fxw-76px-3rxv - CC BY 4.0
Vulnerability history: tensorflow-cpu
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 430
- First → latest
- 04.2019 07.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 6
- High 111
- Medium 208
- Low 105
Disclosures per year
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Memory leak in Tensorflow this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.