CVE-2021-41213: google tensorflow Improper Locking
Vulnerability summary
CVE-2021-41213 is a medium (CVSS 5.5) Improper Locking vulnerability in google tensorflow. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 14.3% of scored vulnerabilities.
Timeline
- 05-11-2021PublishedVulnerability first disclosed.
- 04-08-2024Last modifiedVulnerability information updated.
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.
CVSS metrics
4 scores · 3 sources · 2 versions- OSV · PypiEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- NVDNIST5.5MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.24%
Chance of exploitation in the next 30 days
Percentile
14%
Versus all other CVEs
30-day change
0.00 pp
From 0.24% on 18-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-667Improper LockingThe product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
- CWE-662Improper SynchronizationThe product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.
Affected systems
PyPI3 products
- tensorflow≥ 2.6.0, < 2.6.1 | ≥ 2.5.0, < 2.5.2 | < 2.4.4 | < afac8158d43691661ad083f6dd9e56f327c1dcb7 | ≥ 2.7.0rc0, < 2.7.0
- tensorflow-cpu≥ 2.6.0, < 2.6.1 | ≥ 2.5.0, < 2.5.2 | < 2.4.4 | < afac8158d43691661ad083f6dd9e56f327c1dcb7 | ≥ 2.7.0rc0, < 2.7.0
- tensorflow-gpu≥ 2.6.0, < 2.6.1 | ≥ 2.5.0, < 2.5.2 | < 2.4.4 | < afac8158d43691661ad083f6dd9e56f327c1dcb7 | ≥ 2.7.0rc0, < 2.7.0
Google1 product
- tensorflow≥ 2.4.0, < 2.4.4 | ≥ 2.5.0, < 2.5.2 | ≥ 2.6.0, < 2.6.1 | 2.7.0:rc0 | 2.7.0:rc1
Tensorflow1 product
- tensorflow≥ 2.6.0, < 2.6.1 | ≥ 2.5.0, < 2.5.2 | < 2.4.4
3 vendors · 5 products
References
7 links- github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcfX Refsource CONFIRMWEBAdvisoryThird Party Advisory
- github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7X Refsource MISCWEBFIXPatchThird Party Advisory