<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 07:49:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-41220 — Use after free in `CollectiveReduceV2`</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-41220</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-41220</guid>
    </item>
    <item>
      <title>GHSA-gpfh-jvf9-7wg5 — Use after free / memory leak in `CollectiveReduceV2`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gpfh-jvf9-7wg5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The [async implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/collective_ops.cc#L604-L615) of `CollectiveReduceV2` suffers from a memory leak and a use after free:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf
  
tf.raw_ops.CollectiveReduceV2(
  input=[],
  group_size=[-10, -10, -10],
  group_key=[-10, -10],
  instance_key=[-10],
  ordering_token=[],
  merge_op=&amp;#39;Mul&amp;#39;,
  final_op=&amp;#39;Div&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;This occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed:&lt;/p&gt;
&lt;p&gt;```cc
auto done_with_cleanup = [col_params, done = std::move(done)]() {
  done();
  col_params-&amp;gt;Unref();
};
OP_REQUIRES_OK_ASYNC(c,
                     FillCollectiveParams(col_params, REDUCTION_COLLECTIVE,
                                          /*group_size*/ c-&amp;gt;input(1),
                                          /*group_key*/ c-&amp;gt;input(2),
                                          /*instance_key*/ c-&amp;gt;input(3)),
                     done);
```&lt;/p&gt;
&lt;p&gt;Here, `done` is already moved from by the time `OP_REQUIRES_OK_ASYNC` macro needs to invoke it in case of errors. In this case, we get an undefined behavior, which can manifest via crashes, `std::bad_alloc` throws or just memory leaks.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [ca38dab9d3ee66c5de06f11af9a4b1200da5ef75](https://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75).&lt;/p&gt;
&lt;p&gt;The fix will be in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The [async implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/collective_ops.cc#L604-L615) of `CollectiveReduceV2` suffers from a memory leak and a use after free:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf
  
tf.raw_ops.CollectiveReduceV2(
  input=[],
  group_size=[-10, -10, -10],
  group_key=[-10, -10],
  instance_key=[-10],
  ordering_token=[],
  merge_op=&amp;#39;Mul&amp;#39;,
  final_op=&amp;#39;Div&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;This occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed:&lt;/p&gt;
&lt;p&gt;```cc
auto done_with_cleanup = [col_params, done = std::move(done)]() {
  done();
  col_params-&amp;gt;Unref();
};
OP_REQUIRES_OK_ASYNC(c,
                     FillCollectiveParams(col_params, REDUCTION_COLLECTIVE,
                                          /*group_size*/ c-&amp;gt;input(1),
                                          /*group_key*/ c-&amp;gt;input(2),
                                          /*instance_key*/ c-&amp;gt;input(3)),
                     done);
```&lt;/p&gt;
&lt;p&gt;Here, `done` is already moved from by the time `OP_REQUIRES_OK_ASYNC` macro needs to invoke it in case of errors. In this case, we get an undefined behavior, which can manifest via crashes, `std::bad_alloc` throws or just memory leaks.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [ca38dab9d3ee66c5de06f11af9a4b1200da5ef75](https://github.com/tensorflow/tensorflow/commit/ca38dab9d3ee66c5de06f11af9a4b1200da5ef75).&lt;/p&gt;
&lt;p&gt;The fix will be in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gpfh-jvf9-7wg5</guid>
    </item>
  </channel>
</rss>
