CVE-2024-36976: Revert "media: v4l2-ctrls: show all owned controls in log_status"
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-36976 is a Linux kernel media subsystem issue where a prior change could create a deadlock. In business terms, affected systems may hang in specific media-control paths, causing availability risk rather than a clearly evidenced data breach or code execution issue.
Executive priority
Treat this as a kernel availability issue requiring tracked remediation, not an emergency based on current evidence. Raise priority for production video, camera, capture, or media-processing systems where a hang would affect operations.
Technical view
The vulnerable change was commit 9801b5b28c6929139d6fceeee8d739cc67bb2739 in v4l2-ctrls log_status handling. The kernel fix reverts that change after lockdep reported unsafe ordering between V4L2 control-handler locks, creating a potential deadlock scenario.
Likely exposure
Exposure appears limited to Linux kernels carrying the affected V4L2 media-control change. The bundle marks Linux 6.9-related ranges as affected, but exact distro exposure depends on vendor backports and kernel packaging.
Exploitation context
The bundle does not show KEV listing, active exploitation, CVSS, or a public exploit. The cited evidence describes a potential deadlock, so the supported impact is availability degradation or hang, not confirmed privilege escalation or remote compromise.
Researcher notes
Evidence is narrow but clear: the fix is a revert due to unsafe lock ordering in V4L2 control logging. The bundle lacks CVSS, CWE, exploit details, and distribution-specific fixed versions, so validation should focus on kernel lineage and vendor advisories.
Mitigation direction
Update to a vendor kernel that includes the referenced stable revert.
Check Linux distribution advisories for CVE-2024-36976 package status.
Prioritize systems using V4L2, media devices, capture cards, or camera workloads.
Use normal kernel rollout controls and rollback planning.
Avoid assuming source kernel versions match distribution backports.
Validation and detection
Inventory kernel versions and vendor package revisions across Linux hosts.
Confirm whether vendor changelogs mention CVE-2024-36976 or the stable commits.
Identify hosts exposing V4L2/media hardware or related workloads.
After patching, confirm the running kernel changed after reboot.
Monitor for kernel lockup, media-service hangs, or deadlock warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36976 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.