CVE-2020-26268
Description
In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Arch Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Fixed | 2.4.0-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <1.15.5 | 1.15.5 |
| PyPI | tensorflow | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow-cpu | <1.15.5 | 1.15.5 |
| PyPI | tensorflow-cpu | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow-cpu | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow-cpu | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow-cpu | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow-gpu | <1.15.5 | 1.15.5 |
| PyPI | tensorflow-gpu | >=2.0.0,<2.0.4 | 2.0.4 |
| PyPI | tensorflow-gpu | >=2.1.0,<2.1.3 | 2.1.3 |
| PyPI | tensorflow-gpu | >=2.2.0,<2.2.2 | 2.2.2 |
| PyPI | tensorflow-gpu | >=2.3.0,<2.3.2 | 2.3.2 |
| PyPI | tensorflow-cpu | <c1e1fc899ad5f8c725dcbb6470069890b5060bc7||>=2.3.0,<2.3.2 | c1e1fc899ad5f8c725dcbb6470069890b5060bc7 |
| PyPI | tensorflow | <c1e1fc899ad5f8c725dcbb6470069890b5060bc7||>=2.3.0,<2.3.2 | c1e1fc899ad5f8c725dcbb6470069890b5060bc7 |
| PyPI | tensorflow-gpu | <c1e1fc899ad5f8c725dcbb6470069890b5060bc7||>=2.3.0,<2.3.2 | c1e1fc899ad5f8c725dcbb6470069890b5060bc7 |
References
- https://security.archlinux.org/ASA-202012-22
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hhvc-g5hv-48c6
- https://nvd.nist.gov/vuln/detail/CVE-2020-26268
- https://github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-299.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-334.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-255.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2020-26268
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.