Memory leak in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.3.0 · < 2.3.1< 2.2.1≥ 2.3.0rc0 · < 2.3.1
|
| tensorflow-gpu PyPI |
|
|
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure. The issue occurs because the `status` argument during validation failures is not properly checked. Since each of the above methods can return an error status, the `status` value must be checked before continuing. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
From the CVE record · GitHub_M
TensorFlow's `dlpack.to_dlpack` leaks memory when it receives a list of strings and validation fails. An attacker who can cause that input to be passed could trigger the leak; the input does not establish whether this is reachable over a network or requires authentication or user interaction.
Check deployments using the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu before the fixed versions 2.2.1 or 2.3.1.