CVE-2021-29539: TensorFlow GPU ImmutableConst Segfault

tensorflow-gpu Updated 02 Oct 2025

Summary

14/05/2021
Yes i
Unrated
Not published

CVE-2021-29539: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow-gpu across 5 version ranges.

>= 2.2.0, < 2.3.0rc0 < 2.2.0rc0 >= 2.3.0, < 2.3.4 >= 2.4.0, < 2.4.3 < 4f663d4b8f0bec1b48da6fa091a7d29609980fa4

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-29539 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive set of tools, libraries, and resources for developing and deploying machine learning models. TensorFlow allows users to build and train neural networks, perform data preprocessing, and deploy models in various environments. The TensorFlow GPU package, specifically the tensorflow-gpu PyPI package, is a version of TensorFlow optimized for GPU acceleration. It enables users to leverage the power of GPUs for faster training and inference of machine learning models.

Vulnerability Detail

The vulnerability identified as CVE-2021-29539 affects the TensorFlow GPU package. It arises when calling the tf.raw_ops.ImmutableConst function with a dtype parameter set to tf.resource or tf.variant. This triggers a segmentation fault (segfault) in the implementation code, as it assumes that the tensor contents are pure scalars. The issue has been patched in commit 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will be included in TensorFlow 2.5.0. The vulnerability can have severe consequences, including crashes or unexpected behavior in applications utilizing TensorFlow GPU. It is crucial to address this vulnerability to ensure the stability and reliability of machine learning workflows.

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.2.0rc0 2.2.0rc0
    pip install --upgrade "tensorflow-gpu==2.2.0rc0"
  • >= 2.2.0, < 2.3.0rc0 2.3.0rc0
    pip install --upgrade "tensorflow-gpu==2.3.0rc0"
  • >= 2.3.0, < 2.3.4 2.3.4
    pip install --upgrade "tensorflow-gpu==2.3.4"
  • >= 2.4.0, < 2.4.3 2.4.3
    pip 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

If updating to the latest version of tensorflow-gpu is not immediately feasible, a workaround can be implemented by filtering the dtype argument when using tf.raw_ops.ImmutableConst. By ensuring that only valid scalar types are used, the segfault can be avoided. Here is an example of how to apply the workaround:

def safe_immutable_const(value, dtype):
    valid_dtypes = [tf.float32, tf.float64, tf.int32, tf.int64, tf.bool, tf.string]
    if dtype in valid_dtypes:
        return tf.raw_ops.ImmutableConst(value=value, dtype=dtype)
    else:
        raise ValueError('Invalid dtype')

Conclusion

The CVE-2021-29539 vulnerability in TensorFlow GPU can lead to crashes or unexpected behavior in machine learning applications. It is crucial to update the tensorflow-gpu package to version 2.5.0 or later to fix the vulnerability. Alternatively, a workaround can be implemented by filtering the dtype argument when using tf.raw_ops.ImmutableConst. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow-gpu →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides tools and libraries for building and deploying machine learning models.

The tensorflow-gpu package is a version of TensorFlow optimized for GPU acceleration. It allows users to leverage the power of GPUs for faster training and inference of machine learning models.

The vulnerability can result in a segfault when calling tf.raw_ops.ImmutableConst with certain dtype values. This can lead to crashes or unexpected behavior in applications using TensorFlow GPU.

To fix the vulnerability, update the tensorflow-gpu package to version 2.5.0 or later. This version includes the necessary patch to prevent the segfault.

Yes, a workaround is available. By filtering the dtype argument when using tf.raw_ops.ImmutableConst, the segfault can be avoided. See the 'workaround' section for an example.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow-gpu.

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.2.0rc0 2.2.0rc0
    pip install --upgrade "tensorflow-gpu==2.2.0rc0"
  • >= 2.2.0, < 2.3.0rc0 2.3.0rc0
    pip install --upgrade "tensorflow-gpu==2.3.0rc0"
  • >= 2.3.0, < 2.3.4 2.3.4
    pip install --upgrade "tensorflow-gpu==2.3.4"
  • >= 2.4.0, < 2.4.3 2.4.3
    pip 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback