# CVE-2025-39712: media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval

> A deadlock in the mt9m114 camera driver causes a denial of service when setting or getting frame intervals.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-39712, DEBIAN-CVE-2025-39712, GHSA-7rj5-g3mr-xmp6, ROOT-OS-DEBIAN-13-CVE-2025-39712, ROOT-OS-UBUNTU-2404-CVE-2025-39712, UBUNTU-CVE-2025-39712

## What is CVE-2025-39712?

CVE-2025-39712 is a medium-severity vulnerability in Linux kernel, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-39712?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-39712?

Apply the vendor's patch.

## Is CVE-2025-39712 being exploited?

There is no known exploitation of CVE-2025-39712 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-39712 and fix it if it is affected.

What it is: CVE-2025-39712 is a medium-severity vulnerability in Linux kernel, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-39712 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-39712/ (Markdown: https://insights.sbomify.com/CVE-2025-39712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-39712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-39712
- OSV: https://osv.dev/vulnerability/CVE-2025-39712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-39712/
Summaries are generated and may contain mistakes; the official description above is the record.