Linux Kernel up to 6.18.52 iwlwifi iwl_mvm_build_scan_probe buffer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 1.23- |
Summary
A vulnerability described as very critical has been identified in Linux Kernel up to 5.15.221/6.1.188/6.6.157/6.12.110/6.18.52. This affects the function iwl_mvm_build_scan_probe of the component iwlwifi. The manipulation results in buffer overflow.
This vulnerability is cataloged as CVE-2026-98889. The attack may be launched remotely. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 5.15.221/6.1.188/6.6.157/6.12.110/6.18.52. It has been classified as very critical. Affected is the function iwl_mvm_build_scan_probe of the component iwlwifi. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix sched scan IE sizing Scheduled scan built the probe request before iwl_mvm_scan_fits(), so oversized IEs could be copied into the fixed preq buffer before length validation. Move iwl_mvm_build_scan_probe() after the fits check. Also advertise max_sched_scan_ie_len using iwl_mvm_max_scan_ie_len() so userspace limits account for driver-inserted DS/TPC bytes.
The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-98889 since 09/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 10/23/2026).
Upgrading to version 5.15.222, 6.1.189, 6.6.158, 6.12.111 or 6.18.53 eliminates this vulnerability. Applying the patch f2268060e99f94314b9988dfa17393c2694fa9b2/358eca9a898ad4cce7453e9dcfd005d019a2b01f/05f79cea3b15cfe600b205ddcfd51ebee15d908a/a24417478f90e9f1a4ea24cd4b784afccb56fbae/0a63f98e5163a2ec2822dfb691ee5a6094de08ec/4f155d262b31b9b17e0f9856bdabe0968eb4930f is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.15.221
- 6.1.188
- 6.6.157
- 6.12.110
- 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
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: Buffer overflowCWE: CWE-120 / CWE-119
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.15.222/6.1.189/6.6.158/6.12.111/6.18.53
Patch: f2268060e99f94314b9988dfa17393c2694fa9b2/358eca9a898ad4cce7453e9dcfd005d019a2b01f/05f79cea3b15cfe600b205ddcfd51ebee15d908a/a24417478f90e9f1a4ea24cd4b784afccb56fbae/0a63f98e5163a2ec2822dfb691ee5a6094de08ec/4f155d262b31b9b17e0f9856bdabe0968eb4930f
Timeline
09/25/2026 CVE reserved10/23/2026 Advisory disclosed
10/23/2026 VulDB entry created
10/23/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98889 (🔒)
GCVE (CVE): GCVE-0-2026-98889
GCVE (VulDB): GCVE-100-425724
Entry
Created: 10/23/2026 14:49Changes: 10/23/2026 14:49 (59)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.