Null pointer dereference in TensorFlow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. The implementation of `QuantizedMaxPool` has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow’s QuantizedMaxPool implementation can bind a reference to a null pointer when given user-controlled inputs, causing undefined behavior. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Anyone running the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages in versions below 2.5.3, from 2.6.0 to before 2.6.3, or from 2.7.0 to before 2.7.1 should check their installations.