CVE-2021-29614: TensorFlow GPU - Incorrect Results and Python Interpreter Crash in tf.io.decode_raw

tensorflow-gpu Updated 02 Oct 2025

Summary

14/05/2021
Yes i
Unrated
Not published

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

< 2.1.4 >= 2.2.0, < 2.2.3 >= 2.3.0, < 2.3.3 >= 2.4.0, < 2.4.2 < 698e01511f62a3c185754db78ebce0eee1f0184d

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-29614 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for developing and deploying machine learning models. TensorFlow GPU is a specific package that enables GPU acceleration for TensorFlow. It allows users to leverage the power of GPUs to accelerate their machine learning computations, resulting in faster training and inference times.

Vulnerability Detail

The vulnerability in TensorFlow GPU resides in the implementation of tf.io.decode_raw function. When combining the fixed_length parameter with wider datatypes, the function produces incorrect results and crashes the Python interpreter. The issue stems from a bug in the padded version of the function, which is responsible for decoding raw data. The bug arises from a confusion about pointer arithmetic rules. The code incorrectly computes the width of each output element and determines the size needed for the output tensor. This leads to an out-of-bounds write, causing the interpreter to crash. While the provided reproducer results in a crash, more severe attacks can be mounted using this vulnerability, as it allows writing to periodically placed locations in memory.

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.1.4 2.1.4
    pip install --upgrade "tensorflow-gpu==2.1.4"
  • >= 2.2.0, < 2.2.3 2.2.3
    pip install --upgrade "tensorflow-gpu==2.2.3"
  • >= 2.3.0, < 2.3.3 2.3.3
    pip install --upgrade "tensorflow-gpu==2.3.3"
  • >= 2.4.0, < 2.4.2 2.4.2
    pip install --upgrade "tensorflow-gpu==2.4.2"

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 temporary workaround, users can avoid combining the fixed_length parameter with wider datatypes in the tf.io.decode_raw function. By using narrower datatypes or not specifying the fixed_length parameter, the vulnerability can be mitigated. Here is an example of a workaround that uses a narrower datatype:

import tensorflow as tf

# Instead of:
# raw_data = ...
# decoded_data = tf.io.decode_raw(raw_data, tf.float64, fixed_length=10)

# Use:
raw_data = ...
decoded_data = tf.io.decode_raw(raw_data, tf.float32, fixed_length=10)

Conclusion

In conclusion, the vulnerability in TensorFlow GPU's tf.io.decode_raw function can lead to incorrect results and crashes in the Python interpreter. It is important for users to update their TensorFlow GPU package to the latest patched version once it becomes available. In the meantime, a temporary workaround is provided to mitigate the vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow-gpu →

Share this vulnerability

FAQ

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for developing and deploying machine learning models.

TensorFlow GPU is a specific package that enables GPU acceleration for TensorFlow. It allows users to leverage the power of GPUs to accelerate their machine learning computations, resulting in faster training and inference times.

The vulnerability in TensorFlow GPU can lead to incorrect results and crashes in the Python interpreter. While the provided reproducer results in a crash, more severe attacks can be mounted using this vulnerability, as it allows writing to periodically placed locations in memory.

The fix for this vulnerability will be included in TensorFlow 2.5.0. Users are advised to update their TensorFlow GPU package to the latest patched version once it becomes available.

Yes, as a temporary workaround, users can avoid combining the fixed_length parameter with wider datatypes in the tf.io.decode_raw function. By using narrower datatypes or not specifying the fixed_length parameter, the vulnerability can be mitigated.

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.1.4 2.1.4
    pip install --upgrade "tensorflow-gpu==2.1.4"
  • >= 2.2.0, < 2.2.3 2.2.3
    pip install --upgrade "tensorflow-gpu==2.2.3"
  • >= 2.3.0, < 2.3.3 2.3.3
    pip install --upgrade "tensorflow-gpu==2.3.3"
  • >= 2.4.0, < 2.4.2 2.4.2
    pip install --upgrade "tensorflow-gpu==2.4.2"

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