CVE-2023-54304

What it actually does

The driver calls of_match_device() without checking its return value, allowing a subsequent dereference of a NULL pointer when device tree matching fails.

Why it matters to the business

Systems running affected kernels may experience unexpected crashes or instability when the meson_sm driver loads on certain hardware configurations, leading to downtime and potential loss of availability for workloads relying on those systems.

How an attack unfolds

An attacker with the ability to supply or modify a device tree blob that causes of_match_device() to return NULL can trigger the missing NULL check during driver initialization, resulting in a kernel panic.

How to fix it

Update to a kernel containing commit fba9c24c196310546f13c77ff66d0741155fa771 or later; rebuild and deploy the updated kernel image on all affected systems.

How to confirm the fix worked

Verify the presence of the NULL check after of_match_device() in the meson_sm source and confirm the running kernel was built from a tree that includes the referenced commit.

Typical attack path

1. Gain ability to influence or replace the device tree presented to the kernel at boot
2. Trigger loading or probing of the meson_sm driver
3. Cause of_match_device() to return NULL
4. Trigger the subsequent pointer dereference leading to kernel panic

How to detect it

Search kernel logs for oops or panic messages that reference meson_sm or of_match_device around driver initialization time; review boot logs for device tree related failures on systems using the affected driver.

What your security team should do

• Prioritize patching all systems that include the meson_sm driver in their kernel configuration
• Test the updated kernel in a staging environment before broad deployment
• Monitor for kernel oops or panic reports referencing meson_sm after applying updates