https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 17:16:49 +0000 https://vulnerability.circl.lu/vuln/cve-2025-39712 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval</p> <p>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.</p> <p>In [2] it&#39;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.</p> <p>Remove the lock acquisitions/releases from mt9m114_ifp_get_frame_interval() and mt9m114_ifp_set_frame_interval().</p> <p>[1] drivers/media/v4l2-core/v4l2-subdev.c - line 1129 [2] Documentation/driver-api/media/v4l2-subdev.rst</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval</p> <p>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.</p> <p>In [2] it&#39;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.</p> <p>Remove the lock acquisitions/releases from mt9m114_ifp_get_frame_interval() and mt9m114_ifp_set_frame_interval().</p> <p>[1] drivers/media/v4l2-core/v4l2-subdev.c - line 1129 [2] Documentation/driver-api/media/v4l2-subdev.rst</p> https://vulnerability.circl.lu/vuln/cve-2025-39712