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
Product status
24d756e914fc3418bad7897b0657aefa9ef848e8 (git) before 0d23b548d71e5d76955fdf1d73addd8f6494f602
24d756e914fc3418bad7897b0657aefa9ef848e8 (git) before 41b97490a1656bdc7038d6345a84b08d45deafc6
24d756e914fc3418bad7897b0657aefa9ef848e8 (git) before 298d1471cf83d5a2a05970e41822a2403f451086
6.7
Any version before 6.7
6.12.44 (semver)
6.16.4 (semver)
6.17 (original_commit_for_fix)
References
git.kernel.org/...c/0d23b548d71e5d76955fdf1d73addd8f6494f602
git.kernel.org/...c/41b97490a1656bdc7038d6345a84b08d45deafc6
git.kernel.org/...c/298d1471cf83d5a2a05970e41822a2403f451086
