Segfault on strings tensors with mistmatched dimensions 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.4≥ 2.4.0 · < 2.4.3
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.
From the CVE record · GitHub_M
Affected TensorFlow packages can segfault when Go code creates a string tensor whose encoding fails, such as one with mismatched dimensions. The crash occurs when garbage collection deallocates that tensor; the input does not describe a network attack or authentication requirement.
Engineers using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions >=2.5.0rc0 <2.5.1, >=2.3.0 <2.3.4, or >=2.4.0 <2.4.3 should check their installations.