CVE-2020-26268
Summary
| CVE | CVE-2020-26268 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-12-10 23:15:00 UTC |
| Updated | 2020-12-14 17:40:00 UTC |
| 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. |
Risk And Classification
Problem Types: NVD-CWE-Other
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Tensorflow | All | All | All | All | |
| Application | Tensorflow | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Mark `MemmappedTensorAllocator` as returning opaque handle. · tensorflow/tensorflow@c1e1fc8 · GitHub | MISC | github.com | Patch, Third Party Advisory |
| Write to immutable memory region · Advisory · tensorflow/tensorflow · GitHub | CONFIRM | github.com | Exploit, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 983226 Python (pip) Security Update for tensorflow-gpu (GHSA-hhvc-g5hv-48c6)