The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Suse | — | Upgrade libtensorflow_framework2-gnu-openmpi2-hpcUpgrade tensorflow2_2_1_2-gnu-hpc-develUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-docUpgrade tensorflow2Upgrade tensorflow2-docUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-develUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpcUpgrade libtensorflow_cc2-gnu-hpcUpgrade tensorflow2-gnu-openmpi2-hpcUpgrade tensorflow2_2_1_2-gnu-hpc-docUpgrade tensorflow2-liteUpgrade tensorflow2_2_1_2-gnu-hpcUpgrade libtensorflow2-gnu-openmpi2-hpcUpgrade libtensorflow_cc2-gnu-openmpi2-hpcUpgrade tensorflow2-develUpgrade libtensorflow2Upgrade libtensorflow_cc2Upgrade tensorflow2-gnu-hpcUpgrade libtensorflow_framework2Upgrade libtensorflow_framework2-gnu-hpcUpgrade tensorflow2-lite-develUpgrade libtensorflow2-gnu-hpc | Apr 9, 2021 | Sep 25, 2020 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub