Linux Kernel 5.2.14 kfd_interrupt.c alloc_workqueue null pointer dereference ⚔ [Disputed]

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Linux Kernel 5.2.14. The impacted element is an unknown function of the file drivers/gpu/drm/amd/amdkfd/kfd_interrupt.c. Executing a manipulation of the argument alloc_workqueue as part of Return Value can lead to null pointer dereference. This vulnerability is handled as CVE-2019-16229. The attack can be executed remotely. There is not any exploit available. The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability was found in Linux Kernel 5.2.14 (Operating System). It has been declared as problematic. This vulnerability affects an unknown part of the file drivers/gpu/drm/amd/amdkfd/kfd_interrupt.c. The manipulation of the argument alloc_workqueue as part of a Return Value leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:
drivers/gpu/drm/amd/amdkfd/kfd_interrupt.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference. NOTE: The security community disputes this issues as not being serious enough to be deserving a CVE id
The weakness was released 09/11/2019 (Website). The advisory is shared for download at usn.ubuntu.com. This vulnerability was named CVE-2019-16229 since 09/11/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-140765, VDB-140890, VDB-141092 and VDB-141232. Once again VulDB remains the best source for vulnerability data.
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: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.1
NVD Vector: 🔍
CNA Base Score: 5.4
CNA 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: Null pointer dereferenceCWE: CWE-476 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/11/2019 🔍09/11/2019 🔍
09/12/2019 🔍
08/05/2024 🔍
Sources
Vendor: kernel.orgAdvisory: USN-4284-1
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2019-16229 (🔍)
GCVE (CVE): GCVE-0-2019-16229
GCVE (VulDB): GCVE-100-141676
See also: 🔍
Entry
Created: 09/12/2019 08:32Updated: 08/05/2024 03:34
Changes: 09/12/2019 08:32 (58), 08/21/2020 09:44 (2), 12/19/2023 12:02 (3), 06/04/2024 21:38 (27), 08/05/2024 03:34 (2)
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.