Skip to content
Fencer Intel
medium 5.9

CVE-2022-35960 json

`CHECK` failure in `TensorListReserve` in TensorFlow

published 4y ago modified 2mo ago also BIT-tensorflow-2022-35960 , EUVD-2022-6941 , GHSA-v5xg-3q2c-c2r4 , PYSEC-2026-1036 , PYSEC-2026-3243 , PYSEC-2026-3370

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

TensorFlow is an open source platform for machine learning. In `core/kernels/list_kernels.cc's TensorListReserve`, `num_elements` is assumed to be a tensor of size 1. When a `num_elements` of more than 1 element is provided, then `tf.raw_ops.TensorListReserve` fails the `CHECK_EQ` in `CheckIsAlignedAndSingleElement`. We have patched the issue in GitHub commit b5f6fbfba76576202b72119897561e3bd4f179c7. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

Patch / fix

  • pypi tensorflow 2.7.2, 2.8.1, 2.9.1
  • pypi tensorflow-cpu 2.7.2, 2.8.1, 2.9.1
  • pypi tensorflow-gpu 2.7.2, 2.8.1, 2.9.1
  • bitnami tensorflow 2.7.2
  • google tensorflow 2.7.2

Is CVE-2022-35960 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.7.2
>=2.8.0, <2.8.1
>=2.9.0, <2.9.1
2.7.2
2.8.1
2.9.1
pypi tensorflow-cpu
<2.7.2
>=2.8.0, <2.8.1
>=2.9.0, <2.9.1
2.7.2
2.8.1
2.9.1
pypi tensorflow-gpu
<2.7.2
>=2.8.0, <2.8.1
>=2.9.0, <2.9.1
2.7.2
2.8.1
2.9.1
bitnami tensorflow
>=2.7.0, <2.7.2
>=2.8.0, <=2.8.0
>=2.9.0, <=2.9.0
2.7.2

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.