Null pointer dereference in `MatrixDiagPartOp` in TensorFlow

Summary

TensorFlow is an end-to-end open source platform for machine learning. If a user does not provide a valid padding value to `tf.raw_ops.MatrixDiagPartOp`, then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. We have patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Timeline

1. Aug 12, 2021, 6:10 PM UTCCVE published
2. Aug 4, 2024, 1:23 AM UTCRecord last updated

Affected versions

• tensorflow tensorflow

  From 2.5.0 · fixed in 2.5.1; From 2.4.0 · fixed in 2.4.3; fixed in 2.3.4

• tensorflow-cpuPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

• tensorflowPyPI

  fixed in 2.3.4

• tensorflowPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflowPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflow-cpuPyPI

  fixed in 2.3.4

• tensorflow-cpuPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflow-cpuPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflow-gpuPyPI

  fixed in 2.3.4

• tensorflow-gpuPyPI

  From 2.4.0 · fixed in 2.4.3

• tensorflow-gpuPyPI

  From 2.5.0 · fixed in 2.5.1

• tensorflowPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

• tensorflow-gpuPyPI

  From 2.3.0 · fixed in 2.3.4; From 2.4.0 · fixed in 2.4.3

References 2