CVE-2024-53204

What it actually does

The vulnerability is a missing NULL check after devm_kzalloc in rtk_usb3phy_probe, allowing a NULL pointer dereference that results in a kernel crash or memory corruption on allocation failure.

Why it matters to the business

Affected Linux systems with Realtek USB3 PHY hardware may experience unexpected crashes and downtime; low exploitation likelihood reduces immediate operational risk despite kernel-level impact.

How an attack unfolds

An attacker triggers the USB phy probe function (for example via hardware insertion or module load) under conditions where memory allocation fails, causing the unchecked NULL return to be dereferenced and crashing the kernel.

How to fix it

Apply the upstream fix that adds a NULL check after devm_kzalloc in rtk_usb3phy_probe; upgrade to a kernel release containing the resolution for the affected Realtek USB PHY driver.

How to confirm the fix worked

Inspect the probe function in kernel source for the added NULL check after kzalloc, or reproduce allocation failure during probe to confirm crash is prevented.

Typical attack path

1. Connect or enumerate Realtek USB3 PHY hardware to invoke probe
2. Induce memory allocation failure in the probe path
3. Trigger NULL dereference leading to kernel panic

How to detect it

Search kernel logs and crash dumps for entries referencing rtk_usb3phy_probe or NULL dereference during USB phy initialization; correlate with USB device insertion events.

• rtk_usb3phy_probe
• NULL dereference in phy probe

What your security team should do

• Patch affected kernels on systems using Realtek USB3 PHY hardware
• Monitor kernel logs for USB phy related oops or panics
• Limit physical access to USB ports on high-value systems until updated