CWE
682
Advisory Published
Advisory Published
Updated

CVE-2021-41222: Segfault due to negative splits in `SplitV`

First published: Fri Nov 05 2021(Updated: )

### Impact The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/split_v_op.cc#L49-L205) of `SplitV` can trigger a segfault is an attacker supplies negative arguments: ```python import tensorflow as tf tf.raw_ops.SplitV( value=tf.constant([]), size_splits=[-1, -2] ,axis=0, num_split=2) ``` This occurs whenever `size_splits` contains more than one value and at least one value is negative. ### Patches We have patched the issue in GitHub commit [25d622ffc432acc736b14ca3904177579e733cc6](https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6). 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](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) 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.

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
>=2.4.0<2.4.4
>=2.6.0<2.6.1
=2.7.0-rc0
=2.7.0-rc1
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
TensorFlow Keras>=2.4.0<2.4.4
TensorFlow Keras>=2.6.0<2.6.1
TensorFlow Keras=2.7.0-rc0
TensorFlow Keras=2.7.0-rc1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2021-41222?

    CVE-2021-41222 is considered to be a high severity vulnerability due to the potential for segmentation faults when negative arguments are supplied.

  • How do I fix CVE-2021-41222?

    To fix CVE-2021-41222, upgrade to TensorFlow versions 2.4.4, 2.5.2, or 2.6.1 which address this issue.

  • Which versions of TensorFlow are affected by CVE-2021-41222?

    CVE-2021-41222 affects TensorFlow versions 2.4.0 to 2.4.4, 2.6.0 to 2.6.1, and 2.7.0-rc0 and 2.7.0-rc1.

  • What kind of attacks can CVE-2021-41222 enable?

    CVE-2021-41222 can enable denial of service attacks through segmentation faults caused by improperly handled negative arguments.

  • Is CVE-2021-41222 a problem in both TensorFlow CPU and GPU packages?

    Yes, CVE-2021-41222 is a vulnerability present in both TensorFlow CPU and GPU packages.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203