All reports
Medium

Type confusion leading to `CHECK`-failure based denial of service in TensorFlow

Affected versions

Version ranges need review.

Affected versions
>= 2.8.0, < 2.8.1
Fixed version
2.8.1
Affected versions
< 2.6.4
Fixed version
2.6.4
Affected versions
>= 2.7.0, < 2.7.2
Fixed version
2.7.2
Affected versions
<2.6.4 || >=2.7.0 <2.7.2 || >=2.8.0 <2.8.1
Fixed version
2.6.4 · 2.7.2 · 2.8.1
Affected versions
< 2.6.4
Fixed version
2.6.4
Affected versions
>= 2.7.0, < 2.7.2
Fixed version
2.7.2
Affected versions
>= 2.8.0, < 2.8.1
Fixed version
2.8.1
Affected versions
<2.6.4 || >=2.7.0 <2.7.2 || >=2.8.0 <2.8.1
Fixed version
2.6.4 · 2.7.2 · 2.8.1
Affected versions
<2.6.4 || >=2.7.0 <2.7.2 || >=2.8.0 <2.8.1
Fixed version
2.6.4 · 2.7.2 · 2.8.1
Affected versions
>= 2.7.0, < 2.7.2
Fixed version
2.7.2
Affected versions
>= 2.8.0, < 2.8.1
Fixed version
2.8.1
Affected versions
< 2.6.4
Fixed version
2.6.4

Exploitation

CVE-2022-29209

Probability of exploitation in the next 30 days: 0.40%

FIRST EPSS · 2026-11-19

Description

Impact

The macros that TensorFlow uses for writing assertions (e.g., CHECK_LT, CHECK_GT, etc.) have an incorrect logic when comparing size_t and int values. Due to type conversion rules, several of the macros would trigger incorrectly.

Patches

We have patched the issue in GitHub commit b917181c29b50cb83399ba41f4d938dc369109a1 (merging GitHub PR #55730).

The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported externally via a GitHub issue.

Links