CVE-2026-99543 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

backlight: qcom-wled: Fix NULL pointer dereference in wled_remove()

wled_probe() doesn't set the driver data for the platform device. As a result, platform_get_drvdata() in wled_remove() will return NULL, and the first dereference of it crashes on unbind.

Set the platform device driver data in wled_probe().

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel backlight subsystem contains a critical flaw within the Qualcomm WLED (White LED) driver that results in a null pointer dereference during device removal operations. This vulnerability stems from an incomplete initialization sequence in the probe function, where the necessary driver-specific data is not properly associated with the platform device structure before the driver becomes active. The core issue lies in the asymmetry between the setup and teardown phases of the driver lifecycle. While the remove function relies heavily on retrieving this stored context via standard kernel APIs to safely dismantle resources and release memory allocations, the probe function fails to establish this link by calling dev_set_drvdata or an equivalent mechanism. Consequently, when the device is unbound from its driver, either through manual sysfs intervention or automatic hotplug events, the system attempts to access a pointer that remains uninitialized.

From a technical perspective, the vulnerability manifests as a kernel panic due to a null pointer dereference in the wled_remove function. The platform_get_drvdata call returns NULL because no data was set during initialization. When this NULL value is subsequently used for memory operations or register accesses without prior validation, it triggers an immediate fault that can crash the entire system if not handled by specific exception handlers. This type of error represents a classic resource management failure where assumptions about state consistency are violated due to missing setup steps. The impact extends beyond simple application crashes; in embedded systems and mobile devices utilizing Qualcomm hardware, such instability can lead to device reboots, loss of display functionality, or denial of service for any process relying on the backlight subsystem at that moment.

This flaw aligns with CWE-476, which describes a NULL pointer dereference vulnerability where software incorrectly handles an expected non-null value as if it were null. In the context of ATT&CK techniques, this could be leveraged in scenarios involving local privilege escalation or system stability disruption, although its primary classification remains a reliability and availability issue rather than a direct security exploit vector for remote code execution. The lack of defensive programming practices here highlights a gap in error handling logic where developers assumed successful initialization without verifying the presence of required context structures before proceeding with cleanup routines.

Mitigation strategies primarily involve applying the upstream kernel patch that corrects this oversight by ensuring dev_set_drvdata is called appropriately within wled_probe to store the driver's private data structure into the platform device object. This ensures symmetry between probe and remove functions, allowing safe retrieval during unbinding. For system administrators unable to immediately update the kernel, monitoring for unstable behavior during device removal events can provide early detection indicators. Long-term remediation requires enforcing static analysis tools that check for missing set_drvdata calls in driver probes and implementing rigorous code review processes focused on lifecycle symmetry checks across all platform drivers within the subsystem.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00157

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!