Browse / AI Framework and Platform Flaws / Memory corruption
Memory corruption
159 records in AI Framework and Platform Flaws.
- Heap buffer overflow in Tensorflow Sparse and ragged count ops do not check that weights match the data shape, so they read past the end of the weights heap buffer.
- Segfault and data corruption in tensorflow-lite Negative axis values are converted to indices with a validity check that only runs in debug builds, so release builds read out of bounds.
- Undefined behavior in Tensorflow Invalid input to dlpack.to_dlpack leaves pointers null, and the unchecked error status lets code bind references to null, causing undefined behaviour.
- Memory corruption in Tensorflow dlpack.to_dlpack accepts non-tensor Python objects and reads uninitialized memory, corrupting process memory.
- Segfault in Tensorflow Splits values that do not start at zero cause an out-of-range access to an uninitialised map entry, crashing the process.
- Out-of-bounds read in TensorFlow possibly causing disclosure of the contents of process memory. An integer overflow in the BMP decoder causes an out-of-bounds read that can expose process memory.
- Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow Truncating 64-bit size values to 32-bit in a segment-sum kernel yields negative indices that write past a heap buffer.
- Improper Restriction of Operations within the Bounds of a Memory Buffer in Google TensorFlow A crafted configuration file triggers a heap buffer overflow in the XLA compiler, causing crashes or reads of other process memory.
- Improper Input Validation in Google TensorFlow Overlapping source and destination buffers in a bundled Snappy memcpy call cause out-of-bounds reads that can crash the process or expose nearby memory.