Undefined behavior via `nullptr` reference binding in sparse matrix multiplication
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 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.
From the CVE record · GitHub_M
Affected TensorFlow sparse matrix multiplication code has undefined behavior when either input matrix has a dimension of zero or less. A zero dimension can lead to a write beyond an empty output tensor's heap allocation. The input does not specify attacker access, authentication requirements, or user interaction.
Teams using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu 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 should check their installations.