Write to immutable memory region in TensorFlow
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.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
tensorflowPyPI | < 1.15.5 | 1.15.5 |
tensorflowPyPI | >= 2.0.0, < 2.0.4 | 2.0.4 |
tensorflowPyPI | >= 2.1.0, < 2.1.3 | 2.1.3 |
tensorflowPyPI | >= 2.2.0, < 2.2.2 | 2.2.2 |
tensorflowPyPI | >= 2.3.0, < 2.3.2 | 2.3.2 |
tensorflow-cpuPyPI | < 1.15.5 | 1.15.5 |
tensorflow-cpuPyPI | >= 2.0.0, < 2.0.4 | 2.0.4 |
tensorflow-cpuPyPI | >= 2.1.0, < 2.1.3 | 2.1.3 |
tensorflow-cpuPyPI | >= 2.2.0, < 2.2.2 | 2.2.2 |
tensorflow-cpuPyPI | >= 2.3.0, < 2.3.2 | 2.3.2 |
tensorflow-gpuPyPI | < 1.15.5 | 1.15.5 |
tensorflow-gpuPyPI | >= 2.0.0, < 2.0.4 | 2.0.4 |
tensorflow-gpuPyPI | >= 2.1.0, < 2.1.3 | 2.1.3 |
tensorflow-gpuPyPI | >= 2.2.0, < 2.2.2 | 2.2.2 |
tensorflow-gpuPyPI | >= 2.3.0, < 2.3.2 | 2.3.2 |
Affected products
1- Range: < 1.15.5
Patches
1c1e1fc899ad5Mark `MemmappedTensorAllocator` as returning opaque handle.
1 file changed · +6 −0
tensorflow/core/kernels/immutable_constant_op.cc+6 −0 modified@@ -62,6 +62,12 @@ class MemmappedTensorAllocator : public Allocator { void set_delete_on_deallocate() { delete_on_deallocate_ = true; } + // Make sure tensors or complex types (strings, variants, resources) don't get + // their constructor called via a placement new since that would require + // writing to immutable data. + // See also: tensorflow/core/framework/typed_allocator.h + bool AllocatesOpaqueHandle() const override { return true; } + private: std::unique_ptr<ReadOnlyMemoryRegion> memory_region_; // If there is an error during allocation we keep it in this status.
Vulnerability mechanics
Generated by null/stub on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- github.com/advisories/GHSA-hhvc-g5hv-48c6ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2020-26268ghsaADVISORY
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-299.yamlghsaWEB
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-334.yamlghsaWEB
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-255.yamlghsaWEB
- github.com/tensorflow/tensorflow/commit/c1e1fc899ad5f8c725dcbb6470069890b5060bc7ghsax_refsource_MISCWEB
- github.com/tensorflow/tensorflow/security/advisories/GHSA-hhvc-g5hv-48c6ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.