CVE-2021-41195
Description
TensorFlow is an open source platform for machine learning. In affected versions the implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large. This is similar to CVE-2021-29584 (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using `AddDim`. However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use `AddDimWithStatus`. 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.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 | >=2.6.0,<2.6.1 | 2.6.1 |
| PyPI | tensorflow-cpu | <e9c81c1e1a9cd8dd31f4e83676cab61b60658429||>=2.6.0,<2.6.1 | e9c81c1e1a9cd8dd31f4e83676cab61b60658429 |
| PyPI | tensorflow-gpu | <e9c81c1e1a9cd8dd31f4e83676cab61b60658429||>=2.6.0,<2.6.1 | e9c81c1e1a9cd8dd31f4e83676cab61b60658429 |
| PyPI | tensorflow | <e9c81c1e1a9cd8dd31f4e83676cab61b60658429||>=2.6.0,<2.6.1 | e9c81c1e1a9cd8dd31f4e83676cab61b60658429 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh
- https://nvd.nist.gov/vuln/detail/CVE-2021-41195
- https://github.com/tensorflow/tensorflow/issues/46888
- https://github.com/tensorflow/tensorflow/pull/51733
- https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-844.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-846.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-842.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-41195
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.