Linux Kernel up to 2.6.36 drivers/net/mlx4/port.c mlx4_register_vlan/mlx4_register_mac Variable memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 2.6.36. This vulnerability affects the function mlx4_register_vlan/mlx4_register_mac of the file drivers/net/mlx4/port.c. Performing a manipulation as part of Variable results in memory corruption.
This vulnerability is reported as CVE-2010-5332. The attack is possible to be carried out remotely. No exploit exists.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 2.6.36 (Operating System). It has been classified as critical. This affects the function mlx4_register_vlan/mlx4_register_mac of the file drivers/net/mlx4/port.c. The manipulation as part of a Variable leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel before 2.6.37, an out of bounds array access happened in drivers/net/mlx4/port.c. When searching for a free entry in either mlx4_register_vlan() or mlx4_register_mac(), and there is no free entry, the loop terminates without updating the local variable free thus causing out of array bounds access.
The weakness was disclosed 07/27/2019. This vulnerability is uniquely identified as CVE-2010-5332 since 07/27/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.6.37 eliminates this vulnerability.
The entries VDB-138871, VDB-138870, VDB-138869 and VDB-138868 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.6.0
- 2.6.1
- 2.6.2
- 2.6.3
- 2.6.4
- 2.6.5
- 2.6.6
- 2.6.7
- 2.6.8
- 2.6.9
- 2.6.10
- 2.6.11
- 2.6.12
- 2.6.13
- 2.6.14
- 2.6.15
- 2.6.16
- 2.6.17
- 2.6.18
- 2.6.19
- 2.6.20
- 2.6.21
- 2.6.22
- 2.6.23
- 2.6.24
- 2.6.25
- 2.6.26
- 2.6.27
- 2.6.28
- 2.6.29
- 2.6.30
- 2.6.31
- 2.6.32
- 2.6.33
- 2.6.34
- 2.6.35
- 2.6.36
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.6
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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 2.6.37
Patch: git.kernel.org
Timeline
07/27/2019 🔍07/27/2019 🔍
07/28/2019 🔍
11/13/2023 🔍
Sources
Vendor: kernel.orgAdvisory: K04146019
Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-5332 (🔍)
GCVE (CVE): GCVE-0-2010-5332
GCVE (VulDB): GCVE-100-138867
See also: 🔍
Entry
Created: 07/28/2019 16:31Updated: 11/13/2023 10:12
Changes: 07/28/2019 16:31 (59), 07/14/2020 09:51 (1), 11/13/2023 10:12 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.