Linux Kernel up to 5.3.8 sdma.c sdma_init resource consumption ⚔ [Disputed]

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Linux Kernel up to 5.3.8. Affected by this vulnerability is the function sdma_init of the file drivers/infiniband/hw/hfi1/sdma.c. Executing a manipulation can lead to resource consumption.
This vulnerability is tracked as CVE-2019-19065. The attack can be launched remotely. No exploit exists.
The existence of this vulnerability is still disputed at present.
You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in Linux Kernel up to 5.3.8 (Operating System). This vulnerability affects the function sdma_init of the file drivers/infiniband/hw/hfi1/sdma.c. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. CVE summarizes:
A memory leak in the sdma_init() function in drivers/infiniband/hw/hfi1/sdma.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering rhashtable_init() failures, aka CID-34b3be18a04e. NOTE: This has been disputed as not a vulnerability because "rhashtable_init() can only fail if it is passed invalid values in the second parameter's struct, but when invoked from sdma_init() that is a pointer to a static const struct, so an attacker could only trigger failure if they could corrupt kernel memory (in which case a small memory leak is not a significant problem).
The weakness was disclosed 11/18/2019. This vulnerability was named CVE-2019-19065 since 11/18/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 5.3.9 eliminates this vulnerability.
The entries VDB-145886, VDB-145885, VDB-145884 and VDB-145883 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.7
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: Resource consumptionCWE: CWE-400 / CWE-404
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 5.3.9
Patch: github.com
Timeline
11/18/2019 🔍11/18/2019 🔍
11/18/2019 🔍
08/05/2024 🔍
Sources
Vendor: kernel.orgAdvisory: 34b3be18a04ecdc610aae4c48e5d1b799d8689f6
Status: Not defined
Disputed: 🔍
CVE: CVE-2019-19065 (🔍)
GCVE (CVE): GCVE-0-2019-19065
GCVE (VulDB): GCVE-100-145882
See also: 🔍
Entry
Created: 11/18/2019 17:42Updated: 08/05/2024 06:49
Changes: 11/18/2019 17:42 (40), 11/18/2019 17:47 (18), 02/23/2024 10:03 (6), 02/23/2024 10:06 (1), 06/05/2024 10:30 (25), 08/05/2024 06:49 (2)
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.