Reference binding to `nullptr` in `tf.ragged.cross`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
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.
From the CVE record · GitHub_M
Affected TensorFlow versions bind a reference to nullptr during shape inference for `tf.ragged.cross`, causing undefined behavior. This can occur when the affected shape-inference code runs; the input does not specify an attacker action or whether network access, authentication, or user interaction is required.
Check PyPI tensorflow, tensorflow-cpu, and tensorflow-gpu installations at versions below 2.4.4, from 2.5.0 to below 2.5.2, from 2.6.0 to below 2.6.1, or from 2.7.0rc0 to below 2.7.0.