CVE-2024-35942: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-35942 addresses a vulnerability in the Linux kernel related to the handling of clock domains for the i.MX8MP platform, specifically within the imx8mp_blk driver responsible for block control. The issue arises from improper management of the fdcc clock, which is part of the HDMI RX verification IP. According to the i.MX8MP reference manual and HDMI ADD documentation, the fdcc clock should not be enabled for HDMI TX operations. However, if this clock is disabled before the HDMI or LCDIF (LCD Interface) probe, the LCDIF component fails to receive the necessary pixel clock from the HDMI PHY, leading to errors such as "vblank wait timed out" and kernel warnings logged by the drm_atomic_helper component. This results in display subsystem malfunctions, potentially causing video output failures or degraded graphical performance on affected devices. The fix involves adding the fdcc clock to the LCDIF and HDMI TX power domains to ensure proper clock provisioning and synchronization during initialization and operation. This vulnerability is specific to the Linux kernel's handling of the i.MX8MP SoC's display subsystem clocks and does not appear to have known exploits in the wild at this time.
Potential Impact
For European organizations utilizing embedded systems or devices based on the NXP i.MX8MP platform running Linux—common in industrial automation, automotive infotainment, medical devices, and certain IoT deployments—this vulnerability could lead to display subsystem failures. Such failures might cause system instability, degraded user interfaces, or complete loss of video output, impacting operational continuity and user experience. In critical infrastructure or industrial environments, where visual feedback and monitoring are essential, this could delay response times or complicate troubleshooting. Although the vulnerability does not directly expose systems to remote code execution or data breaches, the resulting denial of service to display components could indirectly affect system availability and reliability. Given the lack of known exploits and the technical nature of the issue, the immediate risk is moderate but should not be overlooked in environments relying on the affected hardware and kernel versions.
Mitigation Recommendations
To mitigate this vulnerability, organizations should: 1) Apply the official Linux kernel patches that add the fdcc clock to the LCDIF and HDMI TX power domains as recommended by the Linux kernel maintainers and NXP. 2) Verify that all devices using the i.MX8MP platform are running updated kernel versions incorporating this fix. 3) Conduct thorough testing of display functionality post-patch to ensure no regressions or residual issues. 4) For custom or embedded Linux distributions, rebuild and redeploy kernels with the fix integrated. 5) Monitor system logs for any display-related errors or warnings that could indicate incomplete mitigation. 6) Engage with device vendors or integrators to confirm firmware and driver updates include this patch. 7) Maintain an inventory of affected devices to prioritize patching efforts and reduce exposure windows. These steps go beyond generic advice by focusing on the specific hardware platform and kernel component involved.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Sweden, Finland
CVE-2024-35942: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-35942 addresses a vulnerability in the Linux kernel related to the handling of clock domains for the i.MX8MP platform, specifically within the imx8mp_blk driver responsible for block control. The issue arises from improper management of the fdcc clock, which is part of the HDMI RX verification IP. According to the i.MX8MP reference manual and HDMI ADD documentation, the fdcc clock should not be enabled for HDMI TX operations. However, if this clock is disabled before the HDMI or LCDIF (LCD Interface) probe, the LCDIF component fails to receive the necessary pixel clock from the HDMI PHY, leading to errors such as "vblank wait timed out" and kernel warnings logged by the drm_atomic_helper component. This results in display subsystem malfunctions, potentially causing video output failures or degraded graphical performance on affected devices. The fix involves adding the fdcc clock to the LCDIF and HDMI TX power domains to ensure proper clock provisioning and synchronization during initialization and operation. This vulnerability is specific to the Linux kernel's handling of the i.MX8MP SoC's display subsystem clocks and does not appear to have known exploits in the wild at this time.
Potential Impact
For European organizations utilizing embedded systems or devices based on the NXP i.MX8MP platform running Linux—common in industrial automation, automotive infotainment, medical devices, and certain IoT deployments—this vulnerability could lead to display subsystem failures. Such failures might cause system instability, degraded user interfaces, or complete loss of video output, impacting operational continuity and user experience. In critical infrastructure or industrial environments, where visual feedback and monitoring are essential, this could delay response times or complicate troubleshooting. Although the vulnerability does not directly expose systems to remote code execution or data breaches, the resulting denial of service to display components could indirectly affect system availability and reliability. Given the lack of known exploits and the technical nature of the issue, the immediate risk is moderate but should not be overlooked in environments relying on the affected hardware and kernel versions.
Mitigation Recommendations
To mitigate this vulnerability, organizations should: 1) Apply the official Linux kernel patches that add the fdcc clock to the LCDIF and HDMI TX power domains as recommended by the Linux kernel maintainers and NXP. 2) Verify that all devices using the i.MX8MP platform are running updated kernel versions incorporating this fix. 3) Conduct thorough testing of display functionality post-patch to ensure no regressions or residual issues. 4) For custom or embedded Linux distributions, rebuild and redeploy kernels with the fix integrated. 5) Monitor system logs for any display-related errors or warnings that could indicate incomplete mitigation. 6) Engage with device vendors or integrators to confirm firmware and driver updates include this patch. 7) Maintain an inventory of affected devices to prioritize patching efforts and reduce exposure windows. These steps go beyond generic advice by focusing on the specific hardware platform and kernel component involved.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-05-17T13:50:33.132Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9828c4522896dcbe221f
Added to database: 5/21/2025, 9:08:56 AM
Last enriched: 6/29/2025, 8:25:40 AM
Last updated: 8/12/2025, 10:32:26 PM
Views: 10
Related Threats
CVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.