CVE-2022-35989:
TensorFlow vulnerable to `CHECK` fail in `MaxPool`
5.9
CVSS ScoreBasic Information
CVE ID
GHSA ID
EPSS Score
-
CWE
Published
9/16/2022
Updated
1/28/2023
KEV Status
No
Technology
Python
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
tensorflow | pip | < 2.7.2 | 2.7.2 |
tensorflow | pip | >= 2.8.0, < 2.8.1 | 2.8.1 |
tensorflow | pip | >= 2.9.0, < 2.9.1 | 2.9.1 |
tensorflow-cpu | pip | < 2.7.2 | 2.7.2 |
tensorflow-cpu | pip | >= 2.8.0, < 2.8.1 | 2.8.1 |
tensorflow-cpu | pip | >= 2.9.0, < 2.9.1 | 2.9.1 |
tensorflow-gpu | pip | < 2.7.2 | 2.7.2 |
tensorflow-gpu | pip | >= 2.8.0, < 2.8.1 | 2.8.1 |
tensorflow-gpu | pip | >= 2.9.0, < 2.9.1 | 2.9.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The GitHub commit patching this vulnerability specifically modifies the MaxPoolingNoMaskOp GPU kernel implementation in maxpooling_op.cc. The added code checks for empty output shapes and returns early, indicating this was the vulnerable code path. The CVE description explicitly mentions GPU kernel failures when ksize exceeds input dimensions, which aligns with the code changes made to handle degenerate pooling outputs. The test case added in pooling_ops_test.py validates this scenario, confirming the affected functionality.