CVE-2021-37657: TensorFlow GPU - Null Pointer Dereference in MatrixDiagV* Operations
Summary
CVE-2021-37657: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow-gpu across 3 version ranges.
>= 2.3.0, < 2.3.4
>= 2.4.0, < 2.4.3
< f2a673bd34f0d64b8e40a551ac78989d16daad09
Fixed in 2.3.4 or 2.4.3, depending on the release line you run. How to fix ↓
Also tracked for
- tensorflow · Bitnami
- tensorflow · PyPI
- tensorflow · PyPI
- tensorflow-cpu · PyPI
The same CVE-2021-37657 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models. The TensorFlow GPU package, available on PyPI, is specifically designed to leverage the power of GPUs for accelerated machine learning computations.
Vulnerability Detail
The vulnerability (CVE-2021-37657) in TensorFlow GPU arises from incomplete validation in the implementation of operations of type tf.raw_ops.MatrixDiagV*. An attacker can exploit this vulnerability by binding a reference to a null pointer in any of these operations. The issue stems from inadequate checks on the number of elements in the tensor k. If k is an empty tensor, code that accesses the first element of the tensor will result in undefined behavior. This vulnerability can lead to crashes, memory corruption, or other unpredictable outcomes.
How To Fix
Latest published version: 2.12.0 as of 22 Oct 2026
pip install --upgrade "tensorflow-gpu==2.12.0"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 2.3.0, < 2.3.42.3.4pip install --upgrade "tensorflow-gpu==2.3.4" -
>= 2.4.0, < 2.4.32.4.3pip install --upgrade "tensorflow-gpu==2.4.3"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a workaround, users can avoid passing an empty tensor as the input to the affected operations. By ensuring that the tensor k is either a scalar or a non-empty vector, the vulnerability can be mitigated. Here is an example of how to check and handle the tensor k before invoking the MatrixDiagV* operations:
import tensorflow as tf
# Check if k is empty
if tf.size(k) == 0:
# Handle empty tensor case
print('k is empty')
else:
# Invoke the MatrixDiagV* operations
result = tf.raw_ops.MatrixDiagV*(input_tensor, k)
print(result)
Conclusion
The vulnerability (CVE-2021-37657) in TensorFlow GPU, which allows for a null pointer dereference in MatrixDiagV* operations, has been addressed by the TensorFlow development team. Users are advised to update their TensorFlow GPU package to one of the patched versions (2.6.0, 2.5.1, 2.4.3, or 2.3.4) to mitigate the vulnerability. A workaround is also available by avoiding the use of empty tensors as input to the affected operations. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tensorflow-gpu →
FAQ
TensorFlow is an open source platform for machine learning that provides a comprehensive set of tools and resources for building and deploying machine learning models.
The TensorFlow GPU package is a specific distribution of TensorFlow that is optimized to leverage the computational power of GPUs for accelerated machine learning computations.
This vulnerability can lead to crashes, memory corruption, or other undefined behavior when certain operations of type tf.raw_ops.MatrixDiagV* are invoked with an empty tensor as input.
To fix this vulnerability, users should update their TensorFlow GPU package to one of the patched versions: TensorFlow 2.6.0, TensorFlow 2.5.1, TensorFlow 2.4.3, or TensorFlow 2.3.4.
Yes, users can avoid passing an empty tensor as input to the affected operations. By ensuring that the tensor k is either a scalar or a non-empty vector, the vulnerability can be mitigated.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow-gpu.