CVE-2020-26268
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2020
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
Write to immutable memory region in TensorFlow
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
tensorflow
- Vendor
- tensorflow
- Product
- tensorflow
- Platforms
- Unknown
- Default status
Unknown
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| < 1.15.5 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.0.0, < 2.0.4 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.1.0, < 2.1.3 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.2.0, < 2.2.2 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.3.0, < 2.3.2 | affected | Unavailable | Unavailable | Unavailable | None listed |