Crash when type cannot be specialized in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the `DCHECK` function 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. 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.
From the CVE record · GitHub_M
TensorFlow can fail to specialize a type during shape inference, causing an assertion failure and crash in both production and debug builds. Someone who can trigger this scenario could cause the crash; the input does not specify whether this requires network or local access, authentication, or user interaction.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu in versions <2.5.3, >=2.6.0 and <2.6.3, or >=2.7.0 and <2.7.1.