CVE-2023-52863

What it actually does

The flaw is a possible NULL pointer dereference in axi_fan_control_irq_handler when the handler runs before the hwmon device has been registered, resulting in a kernel crash.

Why it matters to the business

Affected Linux systems may suffer sudden kernel panics and reboots during device initialization, causing downtime and loss of availability on servers or embedded devices that use the axi-fan-control driver.

How an attack unfolds

An attacker or faulty hardware timing causes the interrupt handler to be invoked early in driver probe before the private data structure is fully initialized; the handler then dereferences a NULL pointer and triggers a kernel oops.

How to fix it

Update the Linux kernel to a version containing commit 7d870088db4863c514a7f8751cd593751983029a or any later stable tree that includes the NULL-check fix in the axi-fan-control driver.

How to confirm the fix worked

Confirm the patch is present by inspecting the axi_fan_control_probe function for the corrected registration order or by exercising device load under interrupt stress and verifying absence of NULL dereference oops.

Typical attack path

1. Reach a state where the axi-fan-control IRQ can fire before hwmon registration completes
2. Invoke the IRQ handler with an uninitialized private data pointer
3. Trigger NULL pointer dereference and kernel panic

How to detect it

Search kernel logs and crash dumps for oops or panic messages containing "axi_fan_control_irq_handler" together with "NULL pointer dereference" around the time of driver initialization.

What your security team should do

• Prioritize kernel upgrades on all systems exposing the axi-fan-control hwmon driver
• Review boot logs for prior NULL pointer dereference events matching the driver
• Apply the fix in custom or downstream kernel trees before the next maintenance window