Use after free in `CollectiveReduceV2`
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.6.1, 2.7.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
From 2.6.0 · fixed in 2.6.1
- tensorflow-cpuPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflowPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflow-gpuPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflowPyPI
From 2.6.0 · fixed in 2.6.1
- tensorflow-cpuPyPI
From 2.6.0 · fixed in 2.6.1
- tensorflow-gpuPyPI
From 2.6.0 · fixed in 2.6.1