Linux Kernel up to 5.0.13 USB Device drivers/usb/misc/yurex.c null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.0.13 and classified as problematic. This impacts an unknown function of the file drivers/usb/misc/yurex.c of the component USB Device Handler. Performing a manipulation results in null pointer dereference. This vulnerability is known as CVE-2019-15216. The attack may be carried out on the physical device. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in Linux Kernel up to 5.0.13 (Operating System). It has been classified as problematic. This affects an unknown part of the file drivers/usb/misc/yurex.c of the component USB Device Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
An issue was discovered in the Linux kernel before 5.0.14. There is a NULL pointer dereference caused by a malicious USB device in the drivers/usb/misc/yurex.c driver.
The weakness was published 08/19/2019 (Website). The advisory is shared at lists.debian.org. This vulnerability is uniquely identified as CVE-2019-15216 since 08/19/2019. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 247815 (Linux Distros Unpatched Vulnerability : CVE-2019-15216), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.0.14 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (247815). Similar entries are available at VDB-138837, VDB-138838, VDB-138839 and VDB-138853. 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: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 247815
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2019-15216
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.0.14
Patch: git.kernel.org
Timeline
08/19/2019 🔍08/19/2019 🔍
08/20/2019 🔍
08/11/2025 🔍
Sources
Vendor: kernel.orgAdvisory: USN-4115-1
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-15216 (🔍)
GCVE (CVE): GCVE-0-2019-15216
GCVE (VulDB): GCVE-100-140325
See also: 🔍
Entry
Created: 08/20/2019 07:14Updated: 08/11/2025 05:31
Changes: 08/20/2019 07:14 (59), 07/31/2020 16:36 (2), 11/26/2023 16:34 (5), 08/11/2025 05:31 (18)
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.