`CHECK`-failures in `TensorByteSize` in Tensorflow
Medium6.5CVE-2022-23582 · Published Feb 10, 2022 · updated Jul 13, 2026
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 A malicious user can cause a denial of service by altering a `SavedModel` such that [`TensorByteSize`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/attr_value_util.cc#L46-L50) would trigger `CHECK` failures. ```cc int64_t TensorByteSize(const TensorProto& t) { // num_elements returns -1 if shape is not fully defined. int64_t num_elems = TensorShape(t.tensor_shape()).num_elements(); return num_elems < 0 ? -1 : num_elems * DataTypeSize(t.dtype()); } ``` `TensorShape` constructor throws a `CHECK`-fail if shape is partial or has a number of elements that would overflow the size of an `int`. The `PartialTensorShape` constructor instead does not cause a `CHECK`-abort if the shape is partial, which is exactly what this function needs to be able to return `-1`. ### Patches We have patched the issue in GitHub commit [c2426bba00a01de6913738df8fa78e0215fcce02](https://github.com/tensorflow/tensorflow/commit/c2426bba00a01de6913738df8fa78e0215fcce02). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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
- Also known as
- BIT-tensorflow-2022-23582, CVE-2022-23582, PYSEC-2022-146, PYSEC-2022-91, PYSEC-2026-3100
- github.com/tensorflow/tensorflow/security/advisories/GHSA-4j82-5ccr-4r8v
- nvd.nist.gov/vuln/detail/CVE-2022-23582
- github.com/tensorflow/tensorflow/commit/c2426bba00a01de6913738df8fa78e0215fcce02
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-91.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-146.yaml
- github.com/tensorflow/tensorflow
- github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/attr_value_util.cc#L46-L50
More TensorFlow advisories
All TensorFlow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 92022 | Use after free in `DecodePng` kernel CVE-2022-23584High7.6fixed in 2.5.3, 2.6.3, 2.7.1 | High7.6 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Out of bounds write in Tensorflow CVE-2022-23566High8.8fixed in 2.5.3, 2.6.3, 2.7.1 | High8.8 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Reachable Assertion in Tensorflow CVE-2022-23564High6.5fixed in 2.5.3, 2.6.3, 2.7.1 | High6.5 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Insecure temporary file in Tensorflow CVE-2022-23563High7.1fixed in 2.5.3, 2.6.3, 2.7.1 | High7.1 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Integer overflow in Tensorflow CVE-2022-23562High7.6fixed in 2.5.3, 2.6.3, 2.7.1 | High7.6 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Out of bounds write in TFLite CVE-2022-23561High8.8fixed in 2.5.3, 2.6.3, 2.7.1 | High8.8 | 2.5.3, 2.6.3, 2.7.1 |