Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
4.8

CVE-2022-41897: TensorFlow crashes with certain pooling inputs

CVE-2022-41897 · published 3 years ago
Summary

TensorFlow versions 2.8.4 through 2.11 can stop working if the FractionalMaxPoolGrad operation receives oversized row or column sequences. This causes the program to read beyond its memory and crash. Update TensorFlow to the latest patched release or apply the provided fix to the listed versions to prevent the crash.

What to do
  • Update google inc. tensorflow to version 2.8.4.
  • Update google inc. tensorflow to version 2.9.3.
  • Update google inc. tensorflow to version 2.10.1.
  • Update google tensorflow-gpu to version 2.9.3.
  • Update google tensorflow-gpu to version 2.10.1.
  • Update google inc. tensorflow-cpu to version 2.9.3.
  • Update google inc. tensorflow-cpu to version 2.10.1.
  • Update google tensorflow-gpu to version 2.8.4.
  • Update google inc. tensorflow-cpu to version 2.8.4.
Affected software
Ecosystem VendorProductAffected versions
pip google inc. tensorflow < 2.8.4
>= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
Fix: upgrade to 2.8.4
pip google tensorflow-gpu >= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
< 2.8.4
Fix: upgrade to 2.9.3
pip google inc. tensorflow-cpu >= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
< 2.8.4
Fix: upgrade to 2.9.3
– google tensorflow < 2.8.4
>= 2.9.0, < 2.9.3
>= 2.10.0, < 2.10.1
cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:*
Original advisory text
`FractionalMaxPoolGrad` Heap out of bounds read in Tensorflow
TensorFlow is an open source platform for machine learning. If `FractionMaxPoolGrad` is given outsize inputs `row_pooling_sequence` and `col_pooling_sequence`, TensorFlow will crash. We have patched the issue in GitHub commit d71090c3e5ca325bdf4b02eb236cfb3ee823e927. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
4.8 Medium
Exploitation
<1% chance of attack within 30 days
Type
CWE-125Out-of-bounds Read
Timeline
Published18 Nov 2022
Updated4 Nov 2026
First seen6 Mar 2026
Sources
Track software like this
Free during beta