CVE-2021-41214: Reference binding to `nullptr` in `tf.ragged.cross`

Published Nov 5, 2021
·
Updated

Impact The shape inference code for tf.ragged.cross has an undefined behavior due to binding a reference to nullptr. In the following scenario, this results in a crash:

python import tensorflow as tf @tf.function def test(): y = tf.ragged.cross([tf.ragged.constant([['1']]),'2']) return y test() Patches We have patched the issue in GitHub commit fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

For more information Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

Other sources

TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for tf.ragged.cross has an undefined behavior due to binding a reference to nullptr. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

Affected Software

12 affected componentsFixes available
pip/tensorflow-gpu<2.4.4
2.4.4
pip/tensorflow-gpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-gpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow-cpu<2.4.4
2.4.4
pip/tensorflow-cpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-cpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow<2.4.4
2.4.4
pip/tensorflow>=2.5.0<2.5.2
2.5.2
pip/tensorflow>=2.6.0<2.6.1
2.6.1
Google TensorFlow<2.4.4
Google TensorFlow>=2.5.0<2.5.2
Google TensorFlow=2.6.0

Event History

Nov 5, 2021
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 10, 2021
Advisory Published
via GitHub·06:58 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-41214?

CVE-2021-41214 has a high severity due to the potential for undefined behavior that can lead to application crashes or security vulnerabilities.

2

How do I fix CVE-2021-41214?

To fix CVE-2021-41214, upgrade to TensorFlow version 2.4.4, 2.5.2, or 2.6.1, depending on the package you are using.

3

What software is affected by CVE-2021-41214?

CVE-2021-41214 affects multiple versions of TensorFlow, specifically those from versions prior to 2.4.4 up to 2.6.0.

4

Is CVE-2021-41214 a critical vulnerability?

While CVE-2021-41214 is not classified as critical, its impact on application stability makes it significant.

5

When was CVE-2021-41214 disclosed?

CVE-2021-41214 was disclosed in 2021 as part of ongoing security audits and updates for TensorFlow.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203