CVE-2024-42282

What it actually does

NULL pointer dereference when alloc_netdev_dummy fails in mtk_probe, causing mtk_free_dev to invoke free_netdev on a NULL dummy_dev pointer.

Why it matters to the business

Kernel module load failure during hardware initialization can trigger a crash on affected systems, leading to device downtime or boot issues in Mediatek-based network hardware.

How an attack unfolds

An attacker with local access triggers the mtk_probe error path by inducing alloc_netdev_dummy failure, resulting in the NULL dereference during subsequent cleanup in mtk_free_dev.

How to fix it

Update the Linux kernel to version 6.10.3 or later, or apply the commit af6bd5c9901b13a26eaf4d57d97a813297791596 in the stable tree; rebuild and reboot with the patched kernel.

How to confirm the fix worked

Verify the running kernel version is at least 6.10.3, confirm the presence of the fix commit in the source tree, and test that mtk_probe error paths no longer call free_netdev on unallocated dummy_dev.

Typical attack path

1. Gain local access to the target system
2. Load or trigger the mediatek net driver probe sequence
3. Force allocation failure for the dummy net device
4. Observe NULL dereference during error-path cleanup

How to detect it

Review kernel logs for oops or panic messages referencing mtk_free_dev, free_netdev, or NULL pointer dereference during mediatek probe; inspect dmesg and syslog for allocation failure paths in mtk_probe.

What your security team should do

• Prioritize kernel upgrade on all systems using the mediatek driver
• Monitor for local crash reports involving mtk_free_dev or dummy_dev
• Restrict local access until patches are deployed