Skip to main content
VulnerabilityPublished Updated

CVE-2025-39712: Linux kernel · media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 19 Nov 2026, 02:21 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

AI-suggested

A fix is available that removes the redundant locking in the mt9m114 driver functions. Users should update to a Linux kernel version that includes this fix once it is released. Until then, avoid operations that trigger get_frame_interval or set_frame_interval on the mt9m114 device to prevent deadlocks.

Description

CVE-2025-39712 addresses a deadlock vulnerability in the Linux kernel media driver for the mt9m114 device. The issue occurs in the get_frame_interval and set_frame_interval functions, where locks are improperly acquired both in the V4L2 subdev core and again within the driver, causing a deadlock. The fix involves removing redundant lock acquisitions in the driver code, aligning with the documented responsibility that the caller manages locking.

References

Community reviews

Loading reviews…