CVE-2023-54025 in Linux
Summary
by MITRE • 12/24/2025
In the Linux kernel, the following vulnerability has been resolved:
wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled
In case WoWlan was never configured during the operation of the system, the hw->wiphy->wowlan_config will be NULL. rsi_config_wowlan() checks whether wowlan_config is non-NULL and if it is not, then WARNs about it. The warning is valid, as during normal operation the rsi_config_wowlan() should only ever be called with non-NULL wowlan_config. In shutdown this rsi_config_wowlan() should only ever be called if WoWlan was configured before by the user.
Add checks for non-NULL wowlan_config into the shutdown hook. While at it, check whether the wiphy is also non-NULL before accessing wowlan_config . Drop the single-use wowlan_config variable, just inline it into function call.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 12/27/2025
The vulnerability described in CVE-2023-54025 resides within the Linux kernel's wireless subsystem, specifically affecting the rsi driver implementation for wireless network interfaces. This issue represents a potential denial of service condition that could arise during system shutdown operations when the wireless subsystem attempts to configure wake-on-wireless capabilities. The flaw manifests when the driver's shutdown hook executes rsi_config_wowlan() function without proper validation of the wireless configuration state, creating a scenario where the system may generate misleading warnings or potentially crash during power-down sequences.
The technical root cause stems from improper null pointer validation within the driver's shutdown handling logic. During normal wireless operation, the wowlan_config structure is properly initialized when users configure wake-on-wireless capabilities, but during system shutdown, the driver attempts to process this configuration even when no prior configuration has occurred. The kernel's wireless subsystem maintains a wiphy structure that contains wowlan_config information, and when this pointer remains NULL due to no prior configuration, the shutdown hook fails to validate this condition before attempting operations. This violates the principle of defensive programming and creates an opportunity for system instability during critical shutdown sequences.
The operational impact of this vulnerability extends beyond simple warning messages to potentially affect system reliability during power management operations. When the shutdown hook encounters a NULL wowlan_config pointer, the rsi_config_wowlan() function generates warnings that may clutter system logs and indicate improper driver state management. More critically, this could lead to incomplete shutdown sequences or system hangs during power-down operations, particularly in embedded systems or devices where proper power management is crucial. The vulnerability affects systems utilizing the rsi wireless driver, which is commonly found in various wireless network adapters and embedded wireless solutions.
Security implications of this vulnerability align with CWE-476, which addresses null pointer dereference issues in software systems. The flaw represents a classic case of inadequate input validation where the driver fails to properly check for valid configuration states before executing operations. From an ATT&CK framework perspective, this vulnerability could potentially be leveraged in denial of service attacks against wireless-enabled systems, particularly in environments where reliable power management is essential. The issue demonstrates poor error handling practices in kernel space code that could be exploited to degrade system availability or cause unexpected behavior during system lifecycle transitions.
Mitigation strategies should focus on implementing proper null pointer validation within the driver's shutdown hook before attempting wireless configuration operations. The fix involves adding explicit checks for non-NULL wowlan_config pointers before calling rsi_config_wowlan() and ensuring that the wiphy structure itself is validated before accessing its configuration members. System administrators should ensure their kernel versions are updated to include the patched driver implementation, which eliminates the single-use variable and directly inlines the configuration check into the function call. Additionally, monitoring system logs for wireless subsystem warnings during shutdown operations can help identify systems that may still be vulnerable to this condition. The fix aligns with kernel security best practices by ensuring proper state validation and preventing improper operations on uninitialized configuration structures during system power management sequences.