Skip to main content
Projects

CVE-2026-86476: GstVideoMeta Plane Overflow

GStreamer libgstvideo

A heap buffer overflow in GStreamer's video frame mapping, reachable from an untrusted GstVideoMeta deserialized over the unixfd IPC path. A lying plane stride turns a tiny allocation into an out-of-bounds read, and on the write side into a path to code execution. Assigned CVE-2026-86476.

Status
Assigned CVE
Identifier
CVE-2026-86476
Touches
GStreamer / libgstvideo / Memory Safety / Deserialization / Heap Overflow

At a glance

A GstVideoMeta describes how a video frame’s planes are laid out in memory: the stride of each plane and where it starts. gst_video_frame_map() trusts that description. When the meta comes from an untrusted source, nothing checks that its strides and offsets actually fit inside the buffer’s backing memory.

Three gaps line up. default_map() checks that one byte exists at each plane offset and nothing more. The meta branch of gst_video_frame_map_id() is missing the size check its no-meta sibling has. And video_meta_deserialize() rebuilds the meta from raw bytes on the unixfd IPC path with no range check at all, reading strides as signed so negatives pass too.

So a peer can hand a stock pipeline a GstVideoMeta whose planes claim to be huge, sitting on a buffer of a few bytes. Any element that reads the frame by those strides, such as videoconvert, walks off the end of the allocation.

  • Class: CWE-787 (out-of-bounds write) and CWE-125 (out-of-bounds read), reached through CWE-502 (deserialization of untrusted data)
  • Confirmed: out-of-bounds read reproduced under AddressSanitizer, faulting inside video_orc_convert_I420_BGRA
  • Demonstrated: the write side bridged end to end to system() on a non-ASan build
  • Affected: libgstvideo in gst-plugins-base (gstvideometa.c, video-frame.c)

Write-ups

Two posts cover this one. A technical breakdown walks through the three missing checks, the reproduction, and the honest gap between the crash and the write primitive. A longer story is about how I found it, including the part of the exploit I do not get credit for.