LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35942: pmdomain: imx8mp-blk-ctrl: imx8mp_blk: Add fdcc clock to hdmimix domain

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects i.MX8MP-based systems where HDMI/LCDIF display initialization can fail because a required clock is disabled too early. The public record describes display errors and kernel warnings, not data theft or remote compromise. Business urgency depends on whether affected embedded devices rely on HDMI or LCD output.

Executive priority

Treat this as targeted maintenance unless affected devices depend on local display output. It does not currently justify emergency response based on the provided evidence, but embedded fleet owners should fold the fix into kernel update planning.

Technical view

The fix adds the fdcc clock to the LCDIF and HDMI TX power domains in the i.MX8MP block controller. Without it, LCDIF may not receive a pixel clock from HDMI PHY before HDMI/LCDIF probe, causing vblank timeouts and DRM warning logs. The affected scope appears tied to i.MX8MP display/power-domain handling.

Likely exposure

Likely exposure is Linux systems using affected kernel versions on NXP i.MX8MP hardware with HDMI/LCDIF display paths. The source bundle does not show broad generic Linux server exposure or affected non-i.MX8MP platforms.

Exploitation context

CISA KEV is false in the provided bundle, and no cited source reports active exploitation. The available evidence describes a resolved kernel functional defect causing display initialization failures and warnings, not a known attacker workflow.

Researcher notes

The record lacks CVSS, CWE, exploitability analysis, and detailed version-range semantics beyond listed kernel versions and stable commits. Validation should focus on commit presence, SoC/display-path applicability, and vendor backport mapping rather than assuming all Linux deployments are exposed.

Mitigation direction

  • Inventory Linux devices using i.MX8MP HDMI or LCDIF display paths.
  • Check vendor kernel advisories for updates containing the referenced stable fixes.
  • Update affected kernels through the device or distribution vendor channel.
  • Prioritize remediation for devices where display availability affects operations or safety.
  • If updates are unavailable, request vendor guidance for supported backports.

Validation and detection

  • Confirm whether deployed devices use i.MX8MP hardware and affected kernel branches.
  • Verify the running kernel includes one of the referenced stable commits or a vendor backport.
  • Review system logs for vblank timeout and drm_atomic_helper warning patterns.
  • After updating, validate HDMI/LCDIF display initialization across normal boot cycles.
Prepared
Confidence
medium
Sources
5

Public sources used

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-35942 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux556f5cf9568af772d494cff24ffaa7ea41e1ab40, 556f5cf9568af772d494cff24ffaa7ea41e1ab40, 556f5cf9568af772d494cff24ffaa7ea41e1ab40unaffected
LinuxLinux5.19, 0, 6.6.27, 6.8.6, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.