CVE-2025-39712: Linux kernel · media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:21 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
- nvd.nist.gov/vuln/detail/CVE-2025-39712 (opens in a new tab)
- git.kernel.org/stable/c/0d23b548d71e5d76955fdf1d73addd8f6494f602 (opens in a new tab)
- git.kernel.org/stable/c/298d1471cf83d5a2a05970e41822a2403f451086 (opens in a new tab)
- git.kernel.org/stable/c/41b97490a1656bdc7038d6345a84b08d45deafc6 (opens in a new tab)