CVE-2022-29192Public exploit

Process crash via non-scalar quantization bounds

Published May 20, 2022 · Updated Apr 22, 2025

Improper input validation in Google TensorFlow allows local users to crash a process through malformed input tensors. With axis set to -1, QuantizeAndDequantizeV4Grad accepts non-scalar input_min or input_max tensors and then reads them through Tensor::scalar, triggering a CHECK failure. Execution of the crafted local API call is required, and the demonstrated consequence is termination of the hosting TensorFlow process rather than data access or modification.

CVSS severity5.5
Medium
EPSS probability0.34%
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

Improper input validation in Google TensorFlow allows local users to crash a process through malformed input tensors. With axis set to -1, QuantizeAndDequantizeV4Grad accepts non-scalar input_min or input_max tensors and then reads them through Tensor::scalar, triggering a CHECK failure. Execution of the crafted local API call is required, and the demonstrated consequence is termination of the hosting TensorFlow process rather than data access or modification.

The record

CVE
CVE-2022-29192
Published
May 20, 2022
Updated
Apr 22, 2025
Vendor
Google
Product
TensorFlow
Classifications
CWE-20, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 20, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 2025Record 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.6.4
  2. Affected versionversion=>= 2.7.0rc0, < 2.7.2
  3. Affected versionversion=>= 2.8.0rc0, < 2.8.1
  4. Affected versionversion=>= 2.9.0rc0, < 2.9.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Google · TensorFlowversion=< 2.6.4; version=>= 2.7.0rc0, < 2.7.2; version=>= 2.8.0rc0, < 2.8.1; version=>= 2.9.0rc0, < 2.9.0

Published CVSS scores

5.5GitHub, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
T1499.004Application or System Exploitation

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