LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29515: Reference binding to null pointer in `MatrixDiag*` ops

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `MatrixDiag*` operations(https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity TensorFlow crash bug. Certain MatrixDiag-related operations failed to check for empty tensor inputs, which could trigger a null pointer condition and disrupt availability. The sources do not indicate data theft, privilege escalation, or remote unauthenticated exploitation.

Executive priority

Handle through normal dependency patching. Escalate only where vulnerable TensorFlow runs in shared or multi-tenant ML systems, because the credible business impact is disruption of workloads rather than compromise of sensitive data.

Technical view

CVE-2021-29515 is a CWE-476 null pointer issue in TensorFlow MatrixDiag* operation handling. Vulnerable versions can bind a reference to a null pointer when tensor arguments are empty. CVSS 3.1 is 2.5, with local attack vector, high complexity, low privileges, and low availability impact.

Likely exposure

Exposure is most likely in ML training, notebook, or serving environments running affected TensorFlow versions, especially where low-privileged users can submit workloads or influence tensor inputs. Public internet exposure is not supported by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. The CVSS vector indicates local access, high attack complexity, and low privileges are required. The supported impact is availability loss only.

Researcher notes

The key evidence is the TensorFlow advisory and fixing commit. The bundle names affected TensorFlow ranges and the planned fixed releases. It does not provide evidence of exploitation in the wild or broader product impact beyond TensorFlow.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 or later where feasible.
  • For supported older branches, apply TensorFlow 2.4.2, 2.3.3, 2.2.3, or 2.1.4.
  • Prioritize shared ML platforms where untrusted users can run TensorFlow workloads.
  • Check vendor advisory for branch-specific guidance before making exceptions.

Validation and detection

  • Inventory TensorFlow versions in applications, notebooks, containers, and CI images.
  • Compare installed versions against the affected version ranges in the advisory.
  • Review whether workloads use MatrixDiag-related TensorFlow operations.
  • Confirm shared ML environments isolate low-privileged users and jobs.
  • Verify upgraded environments run expected unit and model-serving tests.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-29515 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2021-29515Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow< 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3, >= 2.4.0, < 2.4.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.