# CVE-2026-98191: wifi: wlcore: release runtime PM ref on regdomain config failure

> A missing runtime PM reference release in the wlcore Wi-Fi driver can cause resource leaks and potential denial of service when regulatory domain configuration fails.

- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106464, BELL-CVE-2026-98191, DEBIAN-CVE-2026-98191, GHSA-gpvf-h969-vp49, UBUNTU-CVE-2026-98191

## What is CVE-2026-98191?

CVE-2026-98191 is a denial of service vulnerability in Linux, published on 6 Oct 2026. 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: 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.

## Which versions are affected by CVE-2026-98191?


## How do I fix CVE-2026-98191?

Apply the vendor's patch.

## Is CVE-2026-98191 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98191 and fix it if it is affected.

What it is: CVE-2026-98191 is a denial of service vulnerability in Linux, published on 6 Oct 2026. 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-2026-98191 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-2026-98191/ (Markdown: https://insights.sbomify.com/CVE-2026-98191/index.md)
```

## Sources

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

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