| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Linux Kernel 3.x. This affects an unknown part of the file drivers/media/platform/msm/broadcast/tsc.c. The manipulation results in null pointer dereference. This vulnerability is identified as CVE-2015-0573. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in Linux Kernel 3.x (Operating System). Affected is an unknown part of the file drivers/media/platform/msm/broadcast/tsc.c. 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 confidentiality, integrity, and availability. CVE summarizes:
drivers/media/platform/msm/broadcast/tsc.c in the TSC driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via a crafted application that makes a TSC_GET_CARD_STATUS ioctl call.
The weakness was released 08/07/2016 (Website). The advisory is shared for download at us.codeaurora.org. This vulnerability is traded as CVE-2015-0573 since 01/07/2015. The exploitability is told to be easy. The attack needs to be approached locally. A authentication is necessary for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 09/12/2022).
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-90575 and VDB-90574. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 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: 🔍
Patch: us.codeaurora.org
Timeline
01/07/2015 🔍08/07/2016 🔍
08/07/2016 🔍
08/08/2016 🔍
09/12/2022 🔍
Sources
Vendor: kernel.orgAdvisory: us.codeaurora.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-0573 (🔍)
GCVE (CVE): GCVE-0-2015-0573
GCVE (VulDB): GCVE-100-90576
See also: 🔍
Entry
Created: 08/08/2016 15:13Updated: 09/12/2022 14:20
Changes: 08/08/2016 15:13 (49), 03/21/2019 17:17 (10), 09/12/2022 14:20 (2)
Complete: 🔍
Cache ID: 216:21A:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.

No comments yet. Languages: en.
Please log in to comment.