# CVE-2023-54025: wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled

> A null pointer dereference in the Linux kernel RSI WiFi driver during shutdown can cause a system crash if Wake-on-WLAN was not previously configured.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54025, DEBIAN-CVE-2023-54025, GHSA-jhx4-vm77-c4v2, UBUNTU-CVE-2023-54025

## What is CVE-2023-54025?

CVE-2023-54025 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2023-54025?


## How do I fix CVE-2023-54025?

Apply the vendor's patch.

## Is CVE-2023-54025 being exploited?

There is no known exploitation of CVE-2023-54025 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54025 and fix it if it is affected.

What it is: CVE-2023-54025 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54025 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54025/ (Markdown: https://insights.sbomify.com/CVE-2023-54025/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54025
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54025
- OSV: https://osv.dev/vulnerability/CVE-2023-54025

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54025/
Summaries are generated and may contain mistakes; the official description above is the record.