CVE-2021-41219
Description
TensorFlow is an open source platform for machine learning. In affected versions the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to `nullptr`. This occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. 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-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-cpu | <2.4.4 | 2.4.4 |
| PyPI | tensorflow-cpu | <e6cf28c72ba2eb949ca950d834dd6d66bb01cfae||>=2.7.0rc0,<2.7.0 | e6cf28c72ba2eb949ca950d834dd6d66bb01cfae |
| PyPI | tensorflow | <e6cf28c72ba2eb949ca950d834dd6d66bb01cfae||>=2.7.0rc0,<2.7.0 | e6cf28c72ba2eb949ca950d834dd6d66bb01cfae |
| PyPI | tensorflow-gpu | <e6cf28c72ba2eb949ca950d834dd6d66bb01cfae||>=2.7.0rc0,<2.7.0 | e6cf28c72ba2eb949ca950d834dd6d66bb01cfae |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x
- https://nvd.nist.gov/vuln/detail/CVE-2021-41219
- https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-628.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-826.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-411.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-41219
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.