CVE-2025-39712 Affecting kernel-default-vdso package, versions <6.12.0-160000.6.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.03% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES1600-KERNELDEFAULTVDSO-13939045
  • published13 Nov 2025
  • disclosed6 Nov 2025

Introduced: 6 Nov 2025

NewCVE-2025-39712  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 kernel-default-vdso to version 6.12.0-160000.6.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-default-vdso package and not the kernel-default-vdso package as distributed by SLES. See How to fix? for SLES:16.0.0 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval

Getting / Setting the frame interval using the V4L2 subdev pad ops get_frame_interval/set_frame_interval causes a deadlock, as the subdev state is locked in the [1] but also in the driver itself.

In [2] it's described that the caller is responsible to acquire and release the lock in this case. Therefore, acquiring the lock in the driver is wrong.

Remove the lock acquisitions/releases from mt9m114_ifp_get_frame_interval() and mt9m114_ifp_set_frame_interval().

[1] drivers/media/v4l2-core/v4l2-subdev.c - line 1129 [2] Documentation/driver-api/media/v4l2-subdev.rst

CVSS Base Scores

version 3.1