Bug 2569394 - CVE-2026-125706 mingw-gstreamer1-plugins-bad-free: gst-plugins-bad: missing bounds checks in MPEG PS PES header parsing [fedora-43]
Summary: CVE-2026-125706 mingw-gstreamer1-plugins-bad-free: gst-plugins-bad: missing b...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-gstreamer1-plugins-bad-free
Version: 43
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Marc-Andre Lureau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["f68c8b5a-0f2f-45bb-9de7-1...
Depends On:
Blocks: CVE-2026-125706
TreeView+ depends on / blocked
 
Reported: 2026-11-10 10:42 UTC by lcelant
Modified: 2026-11-10 10:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description lcelant 2026-11-10 10:42:09 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

GStreamer-SA-2026-0024 affects the MPEG Program Stream demuxer and resindvd plugin in gst-plugins-bad. Their PES header parsers lack bounds checks before reading or skipping optional header fields; a DTS timestamp is read before its five-byte length check, and timestamp scanning can read beyond its end pointer. A crafted MPEG Program Stream or VOB file can trigger an out-of-bounds read and potentially crash the parsing application. Static comparison of GStreamer 1.28.2 and 1.28.3 confirms the missing checks and their fix in 1.28.3. The static review did not demonstrate an information-disclosure channel or reproduce a crash. Its initial suggestion that an out-of-bounds pointer reaches gst_buffer_fill() was withdrawn after tracing the parser's length bookkeeping. Upstream advisory: https://gstreamer.freedesktop.org/security/sa-2026-0024.html; fix: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/11580.patch. No reporter is named in the public advisory.


Note You need to log in before you can comment on or make changes to this bug.