Null pointer dereference in Grappler's `IsConstant` in Tensorflow

Summary

Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. 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.

Timeline

1. Feb 4, 2022, 10:32 PM UTCCVE published
2. Apr 22, 2025, 3:50 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Apr 22, 2025, 6:25 PM UTCRecord last updated

Affected versions

• tensorflow tensorflow

  From 2.7.0 · fixed in 2.7.1; From 2.6.0 · fixed in 2.6.3; fixed in 2.5.3

• tensorflowPyPI

  fixed in 2.5.3; From 2.6.0 · fixed in 2.6.3; From 2.7.0 · fixed in 2.7.1

• tensorflowPyPI

  fixed in 2.5.3

• tensorflowPyPI

  From 2.6.0 · fixed in 2.6.3

• tensorflowPyPI

  From 2.7.0 · fixed in 2.7.1

• tensorflow-cpuPyPI

  fixed in 2.5.3

• tensorflow-cpuPyPI

  From 2.6.0 · fixed in 2.6.3

• tensorflow-cpuPyPI

  From 2.7.0 · fixed in 2.7.1

• tensorflow-gpuPyPI

  fixed in 2.5.3

• tensorflow-gpuPyPI

  From 2.6.0 · fixed in 2.6.3

• tensorflow-gpuPyPI

  From 2.7.0 · fixed in 2.7.1

• tensorflow-gpuPyPI

  fixed in 2.5.3; From 2.6.0 · fixed in 2.6.3

• tensorflow-cpuPyPI

  fixed in 2.5.3; From 2.6.0 · fixed in 2.6.3

References 5