TensorFlowGHSA-rww7-2gpw-fv6j

Crash when type cannot be specialized in Tensorflow

CVE-2022-23572 · Published Feb 9, 2022 · updated Jul 13, 2026

High6.5

Fix: upgrade to 2.5.3 or later (3 fixed versions below)

Impact

Under certain scenarios, TensorFlow can fail to specialize a type during [shape inference](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L168-L174):

```cc

void InferenceContext::PreInputInit(

const OpDef& op_def, const std::vector<const Tensor*>& input_tensors,

const std::vector<ShapeHandle>& input_tensors_as_shapes) {

const auto ret = full_type::SpecializeType(attrs_, op_def);

DCHECK(ret.status().ok()) << "while instantiating types: " << ret.status();

ret_types_ = ret.ValueOrDie();

// ...

}

However, DCHECK is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the ValueOrDie line. This results in an assertion failure as ret contains an error Status, not a value. In the second case we also get a crash due to the assertion failure.

Patches

We have patched the issue in GitHub commit [cb164786dc891ea11d3a900e90367c339305dc7b](https://github.com/tensorflow/tensorflow/commit/cb164786dc891ea11d3a900e90367c339305dc7b).

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.

For more information

Please consult [our security...

Affected versions

Package	Affected	Fixed in
tensorflow PyPI	< 2.5.3	2.5.3
	>= 2.6.0, < 2.6.3	2.6.3
	>= 2.7.0, < 2.7.1	2.7.1

Details and references

### Impact Under certain scenarios, TensorFlow can fail to specialize a type during [shape inference](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L168-L174): ```cc void InferenceContext::PreInputInit( const OpDef& op_def, const std::vector<const Tensor*>& input_tensors, const std::vector<ShapeHandle>& input_tensors_as_shapes) { const auto ret = full_type::SpecializeType(attrs_, op_def); DCHECK(ret.status().ok()) << "while instantiating types: " << ret.status(); ret_types_ = ret.ValueOrDie(); // ... } ``` However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the `ValueOrDie` line. This results in an assertion failure as `ret` contains an error `Status`, not a value. In the second case we also get a crash due to the assertion failure. ### Patches We have patched the issue in GitHub commit [cb164786dc891ea11d3a900e90367c339305dc7b](https://github.com/tensorflow/tensorflow/commit/cb164786dc891ea11d3a900e90367c339305dc7b). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range. ### 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:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity from: GitHub (reviewed advisory)
Weakness: CWE-617, CWE-754
Also known as: BIT-tensorflow-2022-23572, CVE-2022-23572, PYSEC-2022-136, PYSEC-2022-81, PYSEC-2026-3241

More TensorFlow advisories

All TensorFlow

High 7.6Feb 9, 2022

Use after free in `DecodePng` kernelCVE-2022-23584fixed in 2.5.3 +2 High 8.8Feb 9, 2022

Out of bounds write in TensorflowCVE-2022-23566fixed in 2.5.3 +2 High 6.5Feb 9, 2022

Reachable Assertion in TensorflowCVE-2022-23564fixed in 2.5.3 +2 High 7.1Feb 9, 2022

Insecure temporary file in TensorflowCVE-2022-23563fixed in 2.5.3 +2 High 7.6Feb 9, 2022

Integer overflow in TensorflowCVE-2022-23562fixed in 2.5.3 +2 High 8.8Feb 9, 2022

Out of bounds write in TFLiteCVE-2022-23561fixed in 2.5.3 +2