CVE-2026-125706

Description

A flaw was found in GStreamer's gst-plugins-bad MPEG Program Stream demuxer and resindvd DVD-playback plugin. The PES header parsers do not adequately check remaining data before reading timestamps and optional header fields. Opening a specially crafted MPEG Program Stream file can cause an out-of-bounds read and potentially crash the application, resulting in a denial of service.

Statement

This vulnerability is rated Moderate because processing a crafted MPEG Program Stream can trigger an out-of-bounds read and potentially crash the GStreamer application. A user or media-processing pipeline must open the file; static verification did not demonstrate an attacker-observable information disclosure or an integrity impact. Current manifest-version assessment marks RHEL 7 ELS, the listed RHEL 8 and 9 streams, and RHEL 10.0, 10.2, and 10.3 as affected with fixes deferred under the Moderate policy. RHEL 6 ELS is affected but outside support scope for this severity. RHEL 10.4 and RHIVOS 2.1 and 2.1 Core are not affected because their shipped versions are at or after the upstream fix. Fedora 43 is affected; Fedora 44 and Rawhide are not affected. The resindvd DVD path requires GPL-enabled builds and DVD libraries, while the MPEG Program Stream demuxer can be selected automatically by applications that open untrusted media.

Mitigation

For applications that automatically select GStreamer plugins, set GST_PLUGIN_FEATURE_RANK=mpegpsdemux:NONE in the affected process to prevent automatic selection of the MPEG Program Stream demuxer. Applications that explicitly instantiate mpegpsdemux or rsndvdbin must avoid processing untrusted MPEG Program Stream or DVD input until a fixed package is available. These measures disable affected playback paths and are not a complete fix.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Red Hat CVSS v3 Score Explanation

AV:L/AC:L/PR:N/UI:R/S:U: parsing a crafted local MPEG Program Stream file is deterministic, needs no privileges, requires the file to be opened or processed, and affects the parsing process. C:N: the 1.28.2-to-1.28.3 static code comparison confirmed out-of-bounds reads but did not establish an attacker-observable information-disclosure channel. The initially suspected gst_buffer_fill() copy is blocked when the parser's remaining-length count reaches zero; the upstream advisory's disclosure possibility remains unverified. I:N: no write primitive was found. A:H: unchecked reads can plausibly crash the process when they reach unmapped memory, although no dynamic crash reproduction was performed. Static verification report: GStreamer-SA-2026-0024.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.