CVE-2022-3114

What it actually does

Missing validation of kcalloc() return value in imx_register_uart_clocks allows a null pointer to be dereferenced, resulting in a kernel crash.

Why it matters to the business

Local denial of service on affected Linux systems can interrupt services, require reboots, and reduce availability of embedded or server workloads using i.MX hardware.

How an attack unfolds

An attacker with local access triggers the vulnerable clock registration path, causing the kernel to dereference a null pointer and panic the system.

How to fix it

Upgrade to a patched Linux kernel version that adds the missing return-value check; apply vendor backports if available for the running kernel series.

How to confirm the fix worked

Confirm the presence of the return-value check after kcalloc in imx_register_uart_clocks; test that clock registration no longer crashes the kernel under memory-pressure conditions.

Typical attack path

1. Obtain local user access on a vulnerable Linux kernel
2. Trigger UART clock registration code path in drivers/clk/imx/clk.c
3. kcalloc fails and returns null without check
4. Null dereference occurs leading to kernel panic

How to detect it

Review kernel logs for oops or panic messages referencing imx_register_uart_clocks or clk.c; correlate with local user activity around the time of the crash.

What your security team should do

• Prioritize kernel updates on all i.MX-based systems
• Monitor vendor advisories for backported fixes
• Restrict local access on exposed embedded devices until patched