CVE-2024-50181

What it actually does

The CLK_SET_PARENT_GATE flag on the i.MX7D DRAM mux clock incorrectly disables the clock parent during active DRAM operation when clk API calls attempt parent switches, causing a system hang instead of restricting source changes to low-level assembly.

Why it matters to the business

Affected Debian 11 systems on i.MX7D hardware risk unplanned downtime and potential data corruption from kernel-induced hangs during routine clock synchronization, increasing operational costs until kernels are updated.

How an attack unfolds

An attacker with local privileges invokes clk API functions to request a parent change on the DRAM mux; the erroneous gate flag disables the active clock source, freezing DRAM access and hanging the system without requiring network access or special payloads.

How to fix it

Upgrade the linux package on Debian 11 to version 5.10.234-1 or newer, which removes the CLK_SET_PARENT_GATE flag from the i.MX7D DRAM mux clock definition.

How to confirm the fix worked

Confirm the running kernel version is at least 5.10.234-1, then inspect the clk-imx driver source or runtime clock tree to verify the flag is absent from the DRAM mux definition.

Typical attack path

1. Obtain local execution on target i.MX7D Debian 11 system
2. Load or execute code that calls clk_set_parent on the DRAM mux clock
3. Trigger the gate logic that disables the active parent while DRAM remains in use
4. Observe system hang and denial of service

How to detect it

Review kernel logs for clock framework messages indicating parent gating on DRAM mux clocks and correlate with unexpected system reboots or hangs on i.MX7D hardware; no persistent artifacts remain after reboot.

What your security team should do

• Prioritize kernel upgrade to 5.10.234-1 across all i.MX7D Debian 11 deployments
• Test clock synchronization paths in staging environments before production rollout
• Monitor vendor advisories for any additional i.MX clock-related fixes