Linux Kernel up to 5.19.1 wifi il4965_rs_fill_link_cmd off-by-one

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.19.1 and classified as critical. Affected is the function il4965_rs_fill_link_cmd of the component wifi. The manipulation leads to off-by-one.
This vulnerability is traded as CVE-2022-50180. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Linux Kernel up to 5.19.1 and classified as critical. This issue affects the function il4965_rs_fill_link_cmd of the component wifi. The manipulation with an unknown input leads to a off-by-one vulnerability. Using CWE to declare the problem leads to CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlegacy: 4965: fix potential off-by-one overflow in il4965_rs_fill_link_cmd() As a result of the execution of the inner while loop, the value of 'idx' can be equal to LINK_QUAL_MAX_RETRY_NUM. However, this is not checked after the loop and 'idx' is used to write the LINK_QUAL_MAX_RETRY_NUM size array 'lq_cmd->rs_table[idx]' below in the outer loop. The fix is to check the new value of 'idx' inside the nested loop, and break both loops if index equals the size. Checking it at the start is now pointless, so let's remove it. Detected using the static analysis tool - Svace.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2022-50180 since 06/18/2025. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/01/2025).
Upgrading to version 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch f59e7534e2b11d7c018a412c293897e8417addd4/20be29b99dfed089fe7b8698cd18dfdda6049bd7/73304c7594080362107bea4c0c3b7da2fb134cc4/e7d6cac6967534e1298497e853964b3d3f994ce3/88b551561ded10017dd846c8aeb2296a5119a915/9f1acb3ce0e37e9c38a6060a0570d56d2963e797/b7c39b1a3d4b8d2ba8c13d5ae1303705b03b46d4/a8eb8e6f7159c7c20c0ddac428bde3d110890aa7 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1350). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Avamar
- Dell NetWorker
- Dell Secure Connect Gateway
- IBM QRadar SIEM
Product
Type
Vendor
Name
Version
- 4.14.290
- 4.19.255
- 5.4.210
- 5.10.136
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.18.0
- 5.18.1
- 5.18.2
- 5.18.3
- 5.18.4
- 5.18.5
- 5.18.6
- 5.18.7
- 5.18.8
- 5.18.9
- 5.18.10
- 5.18.11
- 5.18.12
- 5.18.13
- 5.18.14
- 5.18.15
- 5.18.16
- 5.18.17
- 5.19.0
- 5.19.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
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: Off-by-oneCWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
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 4.14.291/4.19.256/5.4.211/5.10.137/5.15.61/5.18.18/5.19.2
Patch: f59e7534e2b11d7c018a412c293897e8417addd4/20be29b99dfed089fe7b8698cd18dfdda6049bd7/73304c7594080362107bea4c0c3b7da2fb134cc4/e7d6cac6967534e1298497e853964b3d3f994ce3/88b551561ded10017dd846c8aeb2296a5119a915/9f1acb3ce0e37e9c38a6060a0570d56d2963e797/b7c39b1a3d4b8d2ba8c13d5ae1303705b03b46d4/a8eb8e6f7159c7c20c0ddac428bde3d110890aa7
Timeline
06/18/2025 Advisory disclosed06/18/2025 CVE reserved
06/18/2025 VulDB entry created
12/01/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50180 (🔒)
GCVE (CVE): GCVE-0-2022-50180
GCVE (VulDB): GCVE-100-313169
CERT Bund: WID-SEC-2025-1350 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 06/18/2025 15:40Updated: 12/01/2025 07:12
Changes: 06/18/2025 15:40 (58), 10/19/2025 23:36 (7), 12/01/2025 07:12 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.