Reference binding to null pointer in `MatrixDiag*` ops
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `MatrixDiag*` operations(https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s MatrixDiag operations do not check whether tensor arguments are empty. Processing an empty tensor may cause a null pointer dereference. The input does not specify whether this can be triggered over a network, requires authentication, or involves user interaction.
Check installations of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages at versions below 2.1.4, 2.2.0 through 2.2.2, 2.3.0 through 2.3.2, or 2.4.0 through 2.4.1.