Use after free in `CollectiveReduceV2`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
2.6.12.7.0| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. In affected versions the async implementation of `CollectiveReduceV2` suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
From the CVE record · GitHub_M
The asynchronous implementation of CollectiveReduceV2 in affected TensorFlow versions can leak memory and access memory after it has been freed. The input does not specify how an attacker could trigger the issue, whether authentication is needed, or whether user interaction is required.
Anyone running PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions >=2.6.0 <2.6.1 or >=2.7.0rc0 <2.7.0 should check their installation.