Advisory

GHSA-h67m-xg8f-fxcf

Also known as: BIT-tensorflow-2021-41213, CVE-2021-41213, PYSEC-2021-405, PYSEC-2021-622, PYSEC-2021-820

Summary

Deadlock in mutually recursive tf.function objects

Details

Impact
The code behind `tf.function` API can be made to deadlock when two tf.function decorated Python functions are mutually recursive:

import tensorflow as tf

@tf.function()               
def fun1(num):
    if num == 1:
        return
    print(num)
    fun2(num-1)

@tf.function()
def fun2(num):
    if num == 0:
        return
    print(num)
    fun1(num-1)

fun1(9)

This occurs due to using a non-reentrant Lock Python object.

Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive tf.function, although this is not a frequent scenario.

Patches
We have patched the issue in GitHub commit afac8158d43691661ad083f6dd9e56f327c1dcb7.

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.

For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2021-11-10 18:59 UTC
Modified
2026-07-08 06:29 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

  • Fixed version 2.6.1
    pip install --upgrade tensorflow==2.6.1

tensorflow

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

  • Fixed version 2.5.2
    pip install --upgrade tensorflow==2.5.2

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

  • Fixed version 2.4.4
    pip install --upgrade tensorflow==2.4.4

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

  • Fixed version 2.6.1
    pip install --upgrade tensorflow-cpu==2.6.1

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

  • Fixed version 2.5.2
    pip install --upgrade tensorflow-cpu==2.5.2

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

  • Fixed version 2.4.4
    pip install --upgrade tensorflow-cpu==2.4.4

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

  • Fixed version 2.6.1
    pip install --upgrade tensorflow-gpu==2.6.1

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 2.5.0, fixed 2.5.2 (ecosystem)

Fixed versions

2.5.2

Fix

  • Fixed version 2.5.2
    pip install --upgrade tensorflow-gpu==2.5.2

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.4.4 (ecosystem)

Fixed versions

2.4.4

Fix

  • Fixed version 2.4.4
    pip install --upgrade tensorflow-gpu==2.4.4

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences