Skip to content
TensorFlowGHSA-qhxx-j73r-qpm2

Uninitialized memory access in TensorFlow

Medium4.4CVE-2020-26266 · Published Dec 10, 2020 · updated Jul 8, 2026

### Impact Under certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to [default initialize the quantized floating point types in Eigen](https://github.com/tensorflow/tensorflow/blob/f70160322a579144950dff1537dcbe3c7c09d6f5/third_party/eigen3/unsupported/Eigen/CXX11/src/FixedPoint/FixedPointTypes.h#L61-L104): ```cc struct QUInt8 { QUInt8() {} // ... uint8_t value; }; struct QInt16 { QInt16() {} // ... int16_t value; }; struct QUInt16 { QUInt16() {} // ... uint16_t value; }; struct QInt32 { QInt32() {} // ... int32_t value; }; ``` ### Patches We have patched the issue in GitHub commit [ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2](https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive. ### For more information Please consult [our security g...

GitHub advisory

Affected versions

PackageAffectedFixed in
tensorflow
PyPI
< 1.15.51.15.5
>= 2.0.0, < 2.0.42.0.4
>= 2.1.0, < 2.1.32.1.3
>= 2.2.0, < 2.2.22.2.2
>= 2.3.0, < 2.3.22.3.2
Details and references

### Impact Under certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to [default initialize the quantized floating point types in Eigen](https://github.com/tensorflow/tensorflow/blob/f70160322a579144950dff1537dcbe3c7c09d6f5/third_party/eigen3/unsupported/Eigen/CXX11/src/FixedPoint/FixedPointTypes.h#L61-L104): ```cc struct QUInt8 { QUInt8() {} // ... uint8_t value; }; struct QInt16 { QInt16() {} // ... int16_t value; }; struct QUInt16 { QUInt16() {} // ... uint16_t value; }; struct QInt32 { QInt32() {} // ... int32_t value; }; ``` ### Patches We have patched the issue in GitHub commit [ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2](https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Severity from
GitHub (reviewed advisory)
Weakness
CWE-908
Also known as
BIT-tensorflow-2020-26266, CVE-2020-26266, PYSEC-2020-254, PYSEC-2020-297, PYSEC-2020-332

More TensorFlow advisories

All TensorFlow
Advisory
Heap out of bounds access in MakeEdge in TensorFlow
Medium4.4Dec 10, 2020
CHECK-fail in LSTM with zero-length input in TensorFlow
Medium4.4Dec 10, 2020
Write to immutable memory region in TensorFlow
Medium4.4Dec 10, 2020
Lack of validation in data format attributes in TensorFlow
Low4.4Dec 10, 2020
Float cast overflow undefined behavior
Medium3.7Nov 13, 2020
Segfault in `tf.quantization.quantize_and_dequantize`
High5.9Nov 13, 2020

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.