[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024061855-CVE-2024-36976-27e0@gregkh>
Date: Tue, 18 Jun 2024 21:23:56 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-36976: Revert "media: v4l2-ctrls: show all owned controls in log_status"
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Revert "media: v4l2-ctrls: show all owned controls in log_status"
This reverts commit 9801b5b28c6929139d6fceeee8d739cc67bb2739.
This patch introduced a potential deadlock scenario:
[Wed May 8 10:02:06 2024] Possible unsafe locking scenario:
[Wed May 8 10:02:06 2024] CPU0 CPU1
[Wed May 8 10:02:06 2024] ---- ----
[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock);
[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock);
[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock);
[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock);
For now just revert.
The Linux kernel CVE team has assigned CVE-2024-36976 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 9801b5b28c69 and fixed in 6.9.2 with commit 2e0ce54a9c5c
Issue introduced in 6.9 with commit 9801b5b28c69 and fixed in 6.10-rc1 with commit eba63df7eb1f
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-36976
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/media/v4l2-core/v4l2-ctrls-core.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/2e0ce54a9c5c7013b1257be044d99cbe7305e9f1
https://git.kernel.org/stable/c/eba63df7eb1f95df6bfb67722a35372b6994928d
Powered by blists - more mailing lists