cve.bz

CVE-2021-41196 google tensorflow: Integer Underflow (Wrap or Wraparound)

5.5 mediumExploit referenceEPSS 0.2%Fix available

Medium (5.5) in google tensorflow. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.4.4, 2.5.2, 2.6.1.

On this page
TensorFlow is an open source platform for machine learning. In affected versions the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-191 Integer Underflow (Wrap or Wraparound)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-41196 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-41196?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-41196?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-41196 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
google:tensorflowbefore 2.4.4
google:tensorflowfrom 2.5.0 before 2.5.2
google:tensorflowfrom 2.6.0 before 2.6.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m539-j985-hcr8PyPItensorflow>=2.6.0 <2.6.12.6.1
GHSA-m539-j985-hcr8PyPItensorflow>=2.5.0 <2.5.22.5.2
GHSA-m539-j985-hcr8PyPItensorflow<2.4.42.4.4
GHSA-m539-j985-hcr8PyPItensorflow-cpu>=2.6.0 <2.6.12.6.1
GHSA-m539-j985-hcr8PyPItensorflow-cpu>=2.5.0 <2.5.22.5.2
GHSA-m539-j985-hcr8PyPItensorflow-cpu<2.4.42.4.4
GHSA-m539-j985-hcr8PyPItensorflow-gpu>=2.6.0 <2.6.12.6.1
GHSA-m539-j985-hcr8PyPItensorflow-gpu>=2.5.0 <2.5.22.5.2
GHSA-m539-j985-hcr8PyPItensorflow-gpu<2.4.42.4.4
PYSEC-2021-389PyPItensorflow<2.4.4
>=2.5.0 <2.5.2
>=2.6.0 <2.6.1
>=2.7.0rc0 <2.7.0
2.4.4, 2.5.2, 2.6.1, 2.7.0
PYSEC-2021-606PyPItensorflow-cpu<2.4.4
>=2.5.0 <2.5.2
>=2.6.0 <2.6.1
>=2.7.0rc0 <2.7.0
2.4.4, 2.5.2, 2.6.1, 2.7.0
PYSEC-2021-804PyPItensorflow-gpu<2.4.4
>=2.5.0 <2.5.2
>=2.6.0 <2.6.1
>=2.7.0rc0 <2.7.0
2.4.4, 2.5.2, 2.6.1, 2.7.0

References

Check your stackJSON