<?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>Fri, 23 Oct 2026 23:48:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-29211 — Segfault in TensorFlow if `tf.histogram_fixed_width` is called with NaN values</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-29211</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. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.histogram_fixed_width` is vulnerable to a crash when the values array contain `Not a Number` (`NaN`) elements. The implementation assumes that all floating point operations are defined and then converts a floating point result to an integer index. If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash. This only occurs on the CPU implementation. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&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. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.histogram_fixed_width` is vulnerable to a crash when the values array contain `Not a Number` (`NaN`) elements. The implementation assumes that all floating point operations are defined and then converts a floating point result to an integer index. If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash. This only occurs on the CPU implementation. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-29211</guid>
    </item>
    <item>
      <title>GHSA-xrp2-fhq4-4q3w — Segfault if `tf.histogram_fixed_width` is called with NaN values in TensorFlow</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xrp2-fhq4-4q3w</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 implementation of [`tf.histogram_fixed_width`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/histogram_op.cc) is vulnerable to a crash when the values array contain `NaN` elements:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf
import numpy as np&lt;/p&gt;
&lt;p&gt;tf.histogram_fixed_width(values=np.nan, value_range=[1,2])
```&lt;/p&gt;
&lt;p&gt;The [implementation](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/histogram_op.cc#L35-L74) assumes that all floating point operations are defined and then converts a floating point result to an integer index:&lt;/p&gt;
&lt;p&gt;```cc
index_to_bin.device(d) =
    ((values.cwiseMax(value_range(0)) - values.constant(value_range(0)))
         .template cast&amp;lt;double&amp;gt;() /
     step)
        .cwiseMin(nbins_minus_1)
        .template cast&amp;lt;int32&amp;gt;();
```&lt;/p&gt;
&lt;p&gt;If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash.&lt;/p&gt;
&lt;p&gt;This only occurs on the CPU implementation.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [e57fd691c7b0fd00ea3bfe43444f30c1969748b5](https://github.com/tensorflow/tensorflow/commit/e57fd691c7b0fd00ea3bfe43444f30c1969748b5).&lt;/p&gt;
&lt;p&gt;The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](…&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 implementation of [`tf.histogram_fixed_width`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/histogram_op.cc) is vulnerable to a crash when the values array contain `NaN` elements:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf
import numpy as np&lt;/p&gt;
&lt;p&gt;tf.histogram_fixed_width(values=np.nan, value_range=[1,2])
```&lt;/p&gt;
&lt;p&gt;The [implementation](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/histogram_op.cc#L35-L74) assumes that all floating point operations are defined and then converts a floating point result to an integer index:&lt;/p&gt;
&lt;p&gt;```cc
index_to_bin.device(d) =
    ((values.cwiseMax(value_range(0)) - values.constant(value_range(0)))
         .template cast&amp;lt;double&amp;gt;() /
     step)
        .cwiseMin(nbins_minus_1)
        .template cast&amp;lt;int32&amp;gt;();
```&lt;/p&gt;
&lt;p&gt;If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash.&lt;/p&gt;
&lt;p&gt;This only occurs on the CPU implementation.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [e57fd691c7b0fd00ea3bfe43444f30c1969748b5](https://github.com/tensorflow/tensorflow/commit/e57fd691c7b0fd00ea3bfe43444f30c1969748b5).&lt;/p&gt;
&lt;p&gt;The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xrp2-fhq4-4q3w</guid>
    </item>
  </channel>
</rss>
