Segfault in `QuantizedRelu` and `QuantizedRelu6`
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.8.0 · < 2.8.1≥ 2.9.0 · < 2.9.1
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. If `QuantizedRelu` or `QuantizedRelu6` are given nonscalar inputs for `min_features` or `max_features`, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 49b3824d83af706df0ad07e4e677d88659756d89. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
From the CVE record · GitHub_M
TensorFlow's QuantizedRelu and QuantizedRelu6 can segfault when min_features or max_features receives a nonscalar input, allowing a denial of service. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check installations of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages at versions below 2.7.2, 2.8.0 through below 2.8.1, or 2.9.0 through below 2.9.1.