CVE-2024-35942: Linux kernel · pmdomain: imx8mp-blk-ctrl: imx8mp_blk: Add fdcc clock to hdmimix domain
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 30 Oct 2026, 16:33 UTC
Thin evidence
One scorer or noneCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
Description
In the Linux kernel, the following vulnerability has been resolved: pmdomain: imx8mp-blk-ctrl: imx8mp_blk: Add fdcc clock to hdmimix domain According to i.MX8MP RM and HDMI ADD, the fdcc clock is part of hdmi rx verification IP that should not enable for HDMI TX. But actually if the clock is disabled before HDMI/LCDIF probe, LCDIF will not get pixel clock from HDMI PHY and print the error logs: [CRTC:39:crtc-2] vblank wait timed out WARNING: CPU: 2 PID: 9 at drivers/gpu/drm/drm_atomic_helper.c:1634 drm_atomic_helper_wait_for_vblanks.part.0+0x23c/0x260 Add fdcc clock to LCDIF and HDMI TX power domains to fix the issue.
References
- nvd.nist.gov/vuln/detail/CVE-2024-35942 (opens in a new tab)
- git.kernel.org/stable/c/697624ee8ad557ab5417f985d2c804241a7ad30d (opens in a new tab)
- git.kernel.org/stable/c/7c280b5fa64fe78a1a1d198b44a2d90bda36ed65 (opens in a new tab)
- git.kernel.org/stable/c/9d3f959b426635c4da50dfc7b1306afd84d23e7c (opens in a new tab)
- git.kernel.org/stable/c/b13c0d871cd878ff53d25507ca535f59ed1f6a2a (opens in a new tab)