CVE-2026-98191
wifi: wlcore: release runtime PM ref on regdomain config failure
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ fa2648a34e73fb7a17fd0a82e0335a9451d8f5c8, < 85ec6c451fe681ac3135dfa43a519f1404ae63adUpgrade to: 85ec6c451fe681ac3135dfa43a519f1404ae63adAffected: ≥ fa2648a34e73fb7a17fd0a82e0335a9451d8f5c8, < 3fbaae01bb7847d8b0124a8bbdb3af865e388d53Upgrade to: 3fbaae01bb7847d8b0124a8bbdb3af865e388d53Affected: ≥ fa2648a34e73fb7a17fd0a82e0335a9451d8f5c8, < c02352e2b5a241c8da89b5f5f1a0ae4d403120edUpgrade to: c02352e2b5a241c8da89b5f5f1a0ae4d403120edAffected: ≥ fa2648a34e73fb7a17fd0a82e0335a9451d8f5c8, < 05b5e297bbf46f92c80da4c2ebe67828ca0d0247Upgrade to: 05b5e297bbf46f92c80da4c2ebe67828ca0d0247 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: wifi: wlcore: release runtime PM ref on regdomain config failure wlcore_regdomain_config() gets a runtime PM reference before sending the regulatory-domain command. When wlcore_cmd_regdomain_config_locked() fails, the function queues recovery and returns without dropping that reference. Release the reference after handling the command result so both success and failure paths balance the preceding pm_runtime_resume_and_get(). The recovery worker takes a separate runtime PM reference and cannot release the reference held here.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/85ec6c451fe681ac3135dfa43a519f1404ae63ad
- git.kernel.org/stable/c/3fbaae01bb7847d8b0124a8bbdb3af865e388d53
- git.kernel.org/stable/c/c02352e2b5a241c8da89b5f5f1a0ae4d403120ed
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI