Linux Kernel 5.2.14 radeon_display.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 marked as problematic has been reported in Linux Kernel 5.2.14. This affects an unknown function of the file drivers/gpu/drm/radeon/radeon_display.c. The manipulation of the argument alloc_workqueue as part of Return Value leads to null pointer dereference. This vulnerability is uniquely identified as CVE-2019-16230. The attack is possible to be carried out remotely. No exploit exists. There are still doubts about whether this vulnerability truly exists.
Details
A vulnerability was found in Linux Kernel 5.2.14 (Operating System). It has been rated as problematic. This issue affects an unknown code of the file drivers/gpu/drm/radeon/radeon_display.c. The manipulation of the argument alloc_workqueue as part of a Return Value leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:
drivers/gpu/drm/radeon/radeon_display.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference. NOTE: A third-party software maintainer states that the work queue allocation is happening during device initialization, which for a graphics card occurs during boot. It is not attacker controllable and OOM at that time is highly unlikely
The weakness was disclosed 09/11/2019. The identification of this vulnerability is CVE-2019-16230 since 09/11/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, 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.
The entries VDB-140765, VDB-140890, VDB-141092 and VDB-141232 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider 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: 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.7
NVD Vector: 🔍
ADP CISA Base Score: 4.7
ADP CISA 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 🔍
05/29/2026 🔍
Sources
Vendor: kernel.orgAdvisory: bugzilla.suse.com
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2019-16230 (🔍)
GCVE (CVE): GCVE-0-2019-16230
GCVE (VulDB): GCVE-100-141677
See also: 🔍
Entry
Created: 09/12/2019 08:32Updated: 05/29/2026 07:02
Changes: 09/12/2019 08:32 (57), 08/21/2020 09:48 (1), 12/19/2023 12:09 (3), 08/05/2024 03:34 (17), 05/29/2026 07:02 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.