media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.446.16.46.17In 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
From the CVE record · Linux
The Linux kernel's mt9m114 media driver can deadlock when the V4L2 subdevice frame-interval operations are called. The caller already holds the subdevice state lock, but the driver tries to acquire it again. The input does not specify whether an attacker can trigger this remotely or whether authentication or user interaction is required.
Engineers running Linux kernels with the mt9m114 media driver should check whether their kernel includes the fix; affected versions are not specified.