CVE-2024-50240

What it actually does

A NULL pointer dereference occurs in the qcom qmp-usb PHY driver during runtime suspend because driver data initialization was removed from the probe function.

Why it matters to the business

Systems using this driver may experience crashes during power management operations if runtime PM is enabled, potentially disrupting USB functionality on affected Linux deployments with low but stable exploit probability.

How an attack unfolds

An attacker with local access enables runtime PM through sysfs and then triggers a runtime suspend to cause the NULL dereference; no widespread exploitation by listed threat actors observed given none maturity and false KEV status.

How to fix it

Update affected packages to fixed versions such as flashplugin-nonfree (Ubuntu:14.04:LTS) to 11.2.202.535ubuntu0.14.04.1; restore driver data initialization at probe time if building from source.

How to confirm the fix worked

Confirm driver data initialization is present in probe function, enable runtime PM manually and test suspend/resume cycles without dereference, verify package version post-update.

Typical attack path

1. Obtain local access to target system
2. Enable runtime PM via sysfs for the driver
3. Trigger runtime suspend operation
4. Trigger NULL pointer dereference crash

How to detect it

Review kernel logs for NULL pointer dereference or oops messages involving qmp-usb or runtime PM callbacks on suspend; check sysfs runtime PM settings.

What your security team should do

• Apply updates to fixed package versions immediately
• Disable runtime PM via sysfs if not required for the driver
• Monitor kernel logs for NULL dereference oops during suspend operations