🛡️ SUSE-SU-2025:1452-1 — libva (CVE-2023-39929)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for libva

This update for libva fixes the following issues:

Update to libva version 2.20.0, which includes security fix for:

  • CVE-2023-39929: Uncontrolled search path may allow an authenticated

user to escalate privilege via local access (bsc#1224413, jsc#PED-11066)

This includes latest version of one of the components needed for

Video (processing) hardware support on Intel GPUs (bsc#1217770)

Update to version 2.20.0:

  • av1: Revise offsets comments for av1 encode
  • drm:
  • Limit the array size to avoid out of range
  • Remove no longer used helpers
  • jpeg: add support for crop and partial decode
  • trace:
  • Add trace for vaExportSurfaceHandle
  • Unlock mutex before return
  • Fix minor issue about printf data type and value range
  • va/backend:
  • Annotate vafool as deprecated
  • Document the vaGetDriver* APIs
  • va/x11/va_fglrx: Remove some dead code
  • va/x11/va_nvctrl: Remove some dead code
  • va:
  • Add new VADecodeErrorType to indicate the reset happended in

the driver

  • Add vendor string on va_TraceInitialize
  • Added Q416 fourcc (three-plane 16-bit YUV 4:4:4)
  • Drop no longer applicable vaGetDriverNames check
  • Fix:don't leak driver names, when override is set
  • Fix:set driver number to be zero if vaGetDriverNames failed
  • Optimize code of getting driver name for all protocols/os

(wayland,x11,drm,win32,android)

  • Remove legacy code paths
  • Remove unreachable 'DRIVER BUG'
  • win32:
  • Only print win32 driver messages in DEBUG builds
  • Remove duplicate adapter_luid entry
  • x11/dri2: limit the array handling to avoid out of range access
  • x11:
  • Allow disabling DRI3 via LIBVA_DRI3_DISABLE env var
  • Implement vaGetDriverNames
  • Remove legacy code paths

Update to 2.19.0:

  • add: Add mono_chrome to VAEncSequenceParameterBufferAV1
  • add: Enable support for license acquisition of multiple protected

playbacks

  • fix: use secure_getenv instead of getenv
  • trace: Improve and add VA trace log for AV1 encode
  • trace: Unify va log message, replace va_TracePrint with va_TraceMsg.

Update to version 2.18.0:

  • doc: Add build and install libva informatio in home page.
  • fix:
  • Add libva.def into distribution package
  • NULL check before calling strncmp.
  • Remove reference to non-existent symbol
  • meson: docs:
  • Add encoder interface for av1
  • Use libva_version over project_version()
  • va:
  • Add VAProfileH264High10
  • Always build with va-messaging API
  • Fix the codying style of CHECK_DISPLAY
  • Remove Android pre Jelly Bean workarounds
  • Remove dummy isValid() hook
  • Remove unused drm_sarea.h include & ANDROID references in

va_dricommon.h

  • va/sysdeps.h: remove Android section
  • x11:
  • Allow disabling DRI3 via LIBVA_DRI3_DISABLe env var
  • Use LIBVA_DRI3_DISABLE in GetNumCandidates

update to 2.17.0:

  • win: Simplify signature for driver name loading
  • win: Rewrite driver registry query and fix some

bugs/leaks/inefficiencies

  • win: Add missing null check after calloc
  • va: Update security disclaimer
  • dep:remove the file .cvsignore
  • pkgconfig: add 'with-legacy' for emgd, nvctrl and fglrx
  • meson: add 'with-legacy' for emgd, nvctrl and fglrx
  • x11: move all FGLRX code to va_fglrx.c
  • x11: move all NVCTRL code to va_nvctrl.c
  • meson: stop using deprecated meson.source_root()
  • meson: stop using configure_file copy=true
  • va: correctly include the win32 (local) headers
  • win: clean-up the coding style
  • va: dos2unix all the files
  • drm: remove unnecessary dri2 version/extension query
  • trace: annotate internal functions with DLL_HIDDEN
  • build/sysdeps: Remove HAVE_GNUC_VISIBILITY_ATTRIBUTE and use _GNUC_

support level attribute instead

  • meson: Check support for -Wl,-version-script and build link_args

accordingly

  • meson: Set va_win32 soversion to '' and remove the install_data rename
  • fix: resouce check null
  • va_trace: Add Win32 memory types in va_TraceSurfaceAttributes
  • va_trace: va_TraceSurfaceAttributes should check the

VASurfaceAttribMemoryType

  • va: Adds Win32 Node and Windows build support
  • va: Adds compat_win32 abstraction for Windows build and prepares va

common code for windows build

  • pkgconfig: Add Win32 package for when WITH_WIN32 is enabled
  • meson: Add with_win32 option, makes libdrm non-mandatory on Win
  • x11: add basic DRI3 support
  • drm: remove VA_DRM_IsRenderNodeFd() helper
  • drm: add radeon drm + radeonsi mesa combo
  • needed for jira#PED-1174 (Video decoding/encoding support

(VA-API, ...) for Intel GPUs is outside of Mesa)

Update to 2.16.0:

  • add: Add HierarchicalFlag & hierarchical_level_plus1 for AV1e.
  • dep: Update README.md to remove badge links
  • dep: Removed waffle-io badge from README to fix broken link
  • dep: Drop mailing list, IRC and Slack
  • autotools: use wayland-scanner private-code

*

Affected software

SUSE-SU-2025:1452-1 is recorded against 1 package.

  • libva (fixed in 2.20.0-150400.3.5.1)

Timeline and source

Published on 5 May 2025 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

www.suse.com (Advisory)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-05-05
Updated 2026-08-20
Modified 2026-02-04
Fix URL N/A

Affected Packages

Software From version Fixed in
libva 2.20.0-150400.3.5.1

Similar Threats

Free Vulnerability Check

Is your site affected by SUSE-SU-2025:1452-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-SU-2025:1452-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesSUSESUSE 2025