Linux Kernel up to 7.3-rc3 wlcore wlcore_regdomain_config release of resource

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.53 |
Summary
A vulnerability labeled as critical has been found in Linux Kernel up to 7.3-rc3. This affects the function wlcore_regdomain_config of the component wlcore. Executing a manipulation can lead to release of resource.
This vulnerability is registered as CVE-2026-98191. It is possible to launch the attack remotely. No exploit is available.
The affected component should be upgraded.
Details
A vulnerability has been found in Linux Kernel up to 7.3-rc3 and classified as critical. This vulnerability affects the function wlcore_regdomain_config of the component wlcore. The manipulation with an unknown input leads to a release of resource vulnerability. The CWE definition for the vulnerability is CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. As an impact it is known to affect availability. CVE summarizes:
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.
The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-98191 since 09/25/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/06/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8 or 7.3-rc4 eliminates this vulnerability. Applying the patch 85ec6c451fe681ac3135dfa43a519f1404ae63ad/3fbaae01bb7847d8b0124a8bbdb3af865e388d53/c02352e2b5a241c8da89b5f5f1a0ae4d403120ed/05b5e297bbf46f92c80da4c2ebe67828ca0d0247/18eb148105f1af9163f5e9758f0a7bc6ab042423/7f1f25b2db14683ab75d0d22c00d6a75ba988b83/a6bb6ad517a0d4db33a0cac9448e3ae9f4008fb4/8a1f3cf89ddcc700e25afe42cfad333059adcc94 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 5.10.270
- 5.15.221
- 6.1.188
- 6.6.157
- 6.12.111
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
- 7.2.6
- 7.2.7
- 7.3-rc1
- 7.3-rc2
- 7.3-rc3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Release of resourceCWE: CWE-772 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.271/5.15.222/6.1.189/6.6.158/6.12.112/6.18.54/7.2.8/7.3-rc4
Patch: 85ec6c451fe681ac3135dfa43a519f1404ae63ad/3fbaae01bb7847d8b0124a8bbdb3af865e388d53/c02352e2b5a241c8da89b5f5f1a0ae4d403120ed/05b5e297bbf46f92c80da4c2ebe67828ca0d0247/18eb148105f1af9163f5e9758f0a7bc6ab042423/7f1f25b2db14683ab75d0d22c00d6a75ba988b83/a6bb6ad517a0d4db33a0cac9448e3ae9f4008fb4/8a1f3cf89ddcc700e25afe42cfad333059adcc94
Timeline
09/25/2026 CVE reserved10/06/2026 Advisory disclosed
10/06/2026 VulDB entry created
10/06/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98191 (🔒)
GCVE (CVE): GCVE-0-2026-98191
GCVE (VulDB): GCVE-100-414130
Entry
Created: 10/06/2026 13:01Changes: 10/06/2026 13:01 (59)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.