cve.bz

CVE-2022-41889 google tensorflow: NULL Pointer Dereference

7.5 highExploit referenceEPSS 0.6%Fix available

High (7.5) in google tensorflow. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.10.1, 2.8.4, 2.9.3.

On this page
TensorFlow is an open source platform for machine learning. If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a `nullptr`, which is not caught. An example can be seen in `tf.compat.v1.extract_volume_patches` by passing in quantized tensors as input `ksizes`. We have patched the issue in GitHub commit e9e95553e5411834d215e6770c81a83a3d0866ce. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
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-2022-41889 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-41889?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-41889?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-2022-41889 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.8.4
google:tensorflowfrom 2.9.0 before 2.9.3
google:tensorflowfrom 2.10.0 before 2.10.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xxcj-rhqg-m46gPyPItensorflow<2.8.42.8.4
GHSA-xxcj-rhqg-m46gPyPItensorflow>=2.9.0 <2.9.32.9.3
GHSA-xxcj-rhqg-m46gPyPItensorflow>=2.10.0 <2.10.12.10.1
GHSA-xxcj-rhqg-m46gPyPItensorflow-cpu<2.8.42.8.4
GHSA-xxcj-rhqg-m46gPyPItensorflow-gpu<2.8.42.8.4
GHSA-xxcj-rhqg-m46gPyPItensorflow-cpu>=2.9.0 <2.9.32.9.3
GHSA-xxcj-rhqg-m46gPyPItensorflow-gpu>=2.9.0 <2.9.32.9.3
GHSA-xxcj-rhqg-m46gPyPItensorflow-cpu>=2.10.0 <2.10.12.10.1
GHSA-xxcj-rhqg-m46gPyPItensorflow-gpu>=2.10.0 <2.10.12.10.1
PYSEC-2026-1050PyPItensorflow-gpu<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1
PYSEC-2026-3262PyPItensorflow<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1
PYSEC-2026-3384PyPItensorflow-cpu<2.8.4
>=2.9.0 <2.9.3
>=2.10.0 <2.10.1
2.8.4, 2.9.3, 2.10.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux2tensorflow2.11.0-1AZL-11528

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

References

Check your stackJSON