CVE-2021-41213
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Arch Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Fixed | 2.6.1-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-cpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-cpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-cpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-gpu | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-gpu | >=2.5.0,<2.5.2 | 2.5.2 |
| PyPI | tensorflow-gpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow | <afac8158d43691661ad083f6dd9e56f327c1dcb7||>=2.7.0rc0,<2.7.0 | afac8158d43691661ad083f6dd9e56f327c1dcb7 |
| PyPI | tensorflow-cpu | <afac8158d43691661ad083f6dd9e56f327c1dcb7||>=2.7.0rc0,<2.7.0 | afac8158d43691661ad083f6dd9e56f327c1dcb7 |
| PyPI | tensorflow-gpu | <afac8158d43691661ad083f6dd9e56f327c1dcb7||>=2.7.0rc0,<2.7.0 | afac8158d43691661ad083f6dd9e56f327c1dcb7 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf
- https://nvd.nist.gov/vuln/detail/CVE-2021-41213
- https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-622.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-820.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-405.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-41213
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.