LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29562: CHECK-fail in `tf.raw_ops.IRFFT`

TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This TensorFlow flaw can let a local, low-privileged attacker crash affected TensorFlow processing through the IRFFT raw operation. The documented impact is limited availability loss, not data theft or code execution. It is low severity but relevant where untrusted users or jobs can run TensorFlow workloads.

Executive priority

Treat this as a low-priority patching item unless TensorFlow runs in shared or user-submitted workload environments. It should be remediated through normal dependency maintenance, with higher urgency for multi-tenant ML platforms.

Technical view

CVE-2021-29562 is a CWE-617 reachable CHECK failure in tf.raw_ops.IRFFT. Affected TensorFlow versions are before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, and 2.4.x before 2.4.2. The CVSS 3.1 score is 2.5 with local attack vector and low availability impact.

Likely exposure

Exposure is most likely in ML services, notebooks, batch workers, or shared compute environments running affected TensorFlow versions where low-privileged users or submitted jobs can exercise TensorFlow operations.

Exploitation context

The source bundle does not show active exploitation, and KEV status is false. The CVSS vector requires local access, high attack complexity, and low privileges. The stated consequence is denial of service from a CHECK failure.

Researcher notes

The issue is specifically tied to tf.raw_ops.IRFFT and a CHECK failure. The referenced commit is the authoritative fix point for code review and backport verification. Sources do not support claims of remote code execution, data exposure, or active exploitation.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 or fixed supported branches: 2.4.2, 2.3.3, 2.2.3, or 2.1.4.
  • Check vendor advisory guidance before choosing any unsupported workaround.
  • Limit untrusted users or jobs from executing TensorFlow workloads until patched.
  • Prioritize shared ML platforms over isolated developer machines.

Validation and detection

  • Inventory TensorFlow versions in applications, notebooks, containers, and lockfiles.
  • Confirm deployed versions are outside the affected ranges listed in the advisory.
  • Review dependency scanners for CVE-2021-29562 coverage and stale TensorFlow packages.
  • Check ML service logs for unexplained TensorFlow process crashes.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-617: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-29562 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2021-29562Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow< 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3, >= 2.4.0, < 2.4.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-617 · source CWE mapping

Reachable Assertion

Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.