Skip to content
Fencer Intel
medium 5.5

CVE-2021-41213 json

Deadlock in mutually recursive `tf.function` objects

published 5y ago modified 2mo ago also BIT-tensorflow-2021-41213 , EUVD-2021-0435 , GHSA-h67m-xg8f-fxcf , PYSEC-2021-405 , PYSEC-2021-622 , PYSEC-2021-820

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

Summary

TensorFlow is an open source platform for machine learning. In affected versions the code behind `tf.function` API can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive. This occurs due to using a non-reentrant `Lock` Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

Patch / fix

  • pypi tensorflow 2.4.4, 2.5.2, 2.6.1, 2.7.0
  • pypi tensorflow-cpu 2.4.4, 2.5.2, 2.6.1, 2.7.0
  • pypi tensorflow-gpu 2.4.4, 2.5.2, 2.6.1, 2.7.0
  • bitnami tensorflow 2.4.4, 2.5.2, 2.6.1
  • google tensorflow 2.4.4, 2.5.2, 2.6.1
  • tensorflow Arch Linux 2.6.1-1

arch linux advisories AVG-2529

Is CVE-2021-41213 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

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
>=2.7.0rc0, <2.7.0
2.6.1
2.5.2
2.4.4
2.7.0
pypi tensorflow-cpu
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
>=2.7.0rc0, <2.7.0
2.6.1
2.5.2
2.4.4
2.7.0
pypi tensorflow-gpu
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
>=2.7.0rc0, <2.7.0
2.6.1
2.5.2
2.4.4
2.7.0
bitnami tensorflow
>=2.4.0, <2.4.4
>=2.5.0, <2.5.2
>=2.6.0, <2.6.1
2.4.4
2.5.2
2.6.1

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.