CVE-2021-29608Public exploit

Process crash via unchecked empty ragged tensors

Published May 14, 2021 · Updated Aug 3, 2024

Memory corruption in Google TensorFlow affected releases allows local users to crash a process through empty RaggedTensorToTensor inputs. The kernel checks only one tensor for emptiness and relies on DCHECK assertions that disappear from release builds, permitting invalid indexing. Reaching the flaw requires local code to invoke the raw operation with malformed tensors; the resulting heap out-of-bounds access or null dereference disrupts that process.

CVSS severity5.3
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in Google TensorFlow affected releases allows local users to crash a process through empty RaggedTensorToTensor inputs. The kernel checks only one tensor for emptiness and relies on DCHECK assertions that disappear from release builds, permitting invalid indexing. Reaching the flaw requires local code to invoke the raw operation with malformed tensors; the resulting heap out-of-bounds access or null dereference disrupts that process.

The record

CVE
CVE-2021-29608
Published
May 14, 2021
Updated
Aug 3, 2024
Vendor
Google
Product
TensorFlow
Classifications
CWE-131
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 14, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.1.4
  2. Affected versionversion=>= 2.2.0, < 2.2.3
  3. Affected versionversion=>= 2.3.0, < 2.3.3
  4. Affected versionversion=>= 2.4.0, < 2.4.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=< 2.1.4; version=>= 2.2.0, < 2.2.3; version=>= 2.3.0, < 2.3.3; version=>= 2.4.0, < 2.4.2

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.6NIST NVDAV:L/AC:L/Au:N/C:P/I:P/A:P
5.3GitHub, Inc.CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-131Incorrect Calculation of Buffer Size

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo