CVE-2022-35996

Floating point exception in `Conv2D` in TensorFlow

HIGH

7.5

CVSS Score

Published: September 16, 2022 at 10:55 PM UTC

Updated: June 17, 2026 at 04:52 AM UTC

2 products affected across 2 vendorsTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.5%

SSVC

No known exploit

Description

TensorFlow is an open source platform for machine learning. If `Conv2D` is given empty `input` and the `filter` and `padding` sizes are valid, the output is all-zeros. This causes division-by-zero floating point exceptions that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 611d80db29dd7b0cfb755772c69d60ae5bca05f9. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tensorflow · Google

95%

v < 2.7.22.8.0 ≤ v < 2.8.12.9.0 ≤ v < 2.9.12.10 rc0 2.10 rc1 2.10 rc2 2.10 rc3

Affected range stops below 2.7.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.8.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.9.1, so it looks safe — our inference, not a vendor statement

TensorFlow · Tensorflow

60%

v < 2.7.2v < 2.8.1v < 2.9.1

Affected range stops below 2.7.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.8.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.9.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/tensorflow/tensorflow/commit/611d80db29dd7b0cfb755772c69d60ae5bca05f9

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/commit/611d80db29dd7b0cfb755772c69d60ae5bca05f9

x_refsource_CONFIRMThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q5jv-m6qw-5g37

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-369

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card