CVE-2021-37690

critical
Published 2021-08-25 ยท Modified 2023-12-06
CVSS v3
โ€”
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
9.5

Description

TensorFlow is an end-to-end open source platform for machine learning. In affected versions when running shape functions, some functions (such as `MutableHashTableShape`) produce extra output information in the form of a `ShapeAndType` struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. `ShapeRefiner` is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. We have patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Predictions

Exploit likelihood
20%
Patch ETA
โ€”

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 with source_tier=community-verified.

OS impact

arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 2.5.1-1
debian Debian Fixed 2 releases
VersionStatusFixed in
sid Fixed 0
forky Fixed 0

Package impact

EcosystemPackageVulnerableFixed
python PyPItensorflow<2.3.42.3.4
python PyPItensorflow-cpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow-cpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow>=2.4.0,<2.4.32.4.3
python PyPItensorflow-cpu<2.3.42.3.4
python PyPItensorflow-gpu<2.3.42.3.4
python PyPItensorflow-gpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow>=2.5.0,<2.5.12.5.1
python PyPItensorflow-gpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow<ee119d4a498979525046fba1c3dd3f13a039fbb1||>=2.4.0,<2.4.3ee119d4a498979525046fba1c3dd3f13a039fbb1
python PyPItensorflow-cpu<ee119d4a498979525046fba1c3dd3f13a039fbb1||>=2.4.0,<2.4.3ee119d4a498979525046fba1c3dd3f13a039fbb1
python PyPItensorflow-gpu<ee119d4a498979525046fba1c3dd3f13a039fbb1||>=2.4.0,<2.4.3ee119d4a498979525046fba1c3dd3f13a039fbb1

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.