Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 1b51236aa49a0564280bd45c94118cab6d9b0fbd, 4391fa180856ff84a2cef4a92694a689eebb855e, b241e260820b68c09586e8a0ae0fc23c0e3215bd.

Low priority for now. Upgrade to Linux Linux 1b51236aa49a0564280bd45c94118cab6d9b0fbd, 4391fa180856ff84a2cef4a92694a689eebb855e, b241e260820b68c09586e8a0ae0fc23c0e3215bd or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54025

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before b2aeb97fd470206e67f7b3b4a3e68212a13f747baffected · git
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before 4391fa180856ff84a2cef4a92694a689eebb855eaffected · git
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before eb205a06908122f50b1dd1baa43f7c8036bfc7dcaffected · git
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before 1b51236aa49a0564280bd45c94118cab6d9b0fbdaffected · git
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before b601468539c1d97539097bfc87ad11f1704b7eb7affected · git
    • 16bbc3eb83728c03138191a5d23d84d38175fa26 and later · before b241e260820b68c09586e8a0ae0fc23c0e3215bdaffected · git
    • before 5.7not affected · semver
    • 5.10.188 and later · up to and including 5.10.*not affected · semver
    • 5.15.121 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.4-16.4.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54023Dec 24, 2025 · btrfs: fix race between balance and cancel/pause
    0Monitor
  • ← EarlierCVE-2023-54024Dec 24, 2025 · KVM: Destroy target device if coalesced MMIO unregistration fails
    0Monitor
  • Later →CVE-2023-54026Dec 24, 2025 · opp: Fix use-after-free in lazy_opp_tables after probe deferral
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1b51236aa49a0564280bd45c94118cab6d9b0fbdVendor (CNA)
Linux Linux4391fa180856ff84a2cef4a92694a689eebb855eVendor (CNA)
Linux Linuxb241e260820b68c09586e8a0ae0fc23c0e3215bdVendor (CNA)
Linux Linuxb2aeb97fd470206e67f7b3b4a3e68212a13f747bVendor (CNA)
Linux Linuxb601468539c1d97539097bfc87ad11f1704b7eb7Vendor (CNA)
Linux Linuxeb205a06908122f50b1dd1baa43f7c8036bfc7dcVendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records