Skip to content
Fencer Intel
high 7.2

CVE-2015-5198 json

libvdpau before 1.1.1, when used in a setuid or setgid application, allows local users to gain privileges via unspecified vectors, related…

published 11y ago modified 4mo ago also EUVD-2015-5199

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

libvdpau before 1.1.1, when used in a setuid or setgid application, allows local users to gain privileges via unspecified vectors, related to the VDPAU_DRIVER_PATH environment variable.

Patch / fix

  • libvdpau Debian 14, Debian 13, Debian 12 1.1.1-1

debian advisories DEBIAN-CVE-2015-5198

  • libvdpau Ubuntu 14.04 LTS 0.7-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2015-5198

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libvdpau SLED 11 SP4, SLED 11 SP3 0.4.1-16.20.2
  • libvdpau SLES for SAP 12, SLES 12, SLED 12 +2 more 0.8-3.1

suse advisories SUSE-SU-2015:1925-1SUSE-SU-2015:1892-1

Is CVE-2015-5198 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-5198 updated cvss 6.2

libvdpau incorrect check for security transition

  • Red Hat Enterprise Linux 7 libvdpau
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.