CVE-2021-41219: Undefined behavior via `nullptr` reference binding in sparse matrix multiplication

Published Nov 5, 2021
·
Updated

Impact The code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to nullptr:

python import tensorflow as tf tf.rawops.SparseMatMul( a=[[1.0,1.0,1.0]], b=[[],[],[]], transposea=False, transposeb=False, aissparse=False, bissparse=True)

This occurs whenever the dimensions of a or b are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.

Patches We have patched the issue in GitHub commit e6cf28c72ba2eb949ca950d834dd6d66bb01cfae.

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 code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to nullptr. This occurs whenever the dimensions of a or b are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. 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.

MITRE

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
Nov 10, 2021
Advisory Published
via GitHub·06:51 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-41219?

CVE-2021-41219 has a CVSS score that indicates it is a high severity vulnerability.

2

How do I fix CVE-2021-41219?

To fix CVE-2021-41219, update your version of TensorFlow to 2.4.4, 2.5.2, or 2.6.1 depending on your current version.

3

What software is affected by CVE-2021-41219?

CVE-2021-41219 affects TensorFlow versions prior to 2.4.4, 2.5.0 to 2.5.2, and 2.6.0.

4

What kind of vulnerability is CVE-2021-41219?

CVE-2021-41219 is a vulnerability that can lead to undefined behavior due to a reference being bound to a null pointer.

5

Is there a patch available for CVE-2021-41219?

Yes, patches for CVE-2021-41219 are available in the updated TensorFlow releases.

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