CVE-2020-26268

Write to immutable memory region in TensorFlow

State
Published
Severity
4.4 Medium
Published
Dec 10, 2020
Updated
Aug 4, 2024
Reserved
Oct 1, 2020

Read the record on cve.org

Description

In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Scores

CVSSScoreVectorSource
3.14.4 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LGitHub_M

Weaknesses

  • CWE-471 Modification of Assumed-Immutable Data (MAID)

Affected Products

ProductVersions
tensorflowtensorflow
  • < 1.15.5Affected
  • >= 2.0.0, < 2.0.4Affected
  • >= 2.1.0, < 2.1.3Affected
  • >= 2.2.0, < 2.2.2Affected
  • >= 2.3.0, < 2.3.2Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.