Linux Kernel up to 5.9.13 Locking drivers/tty/tty_io.c use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.9.13. It has been rated as critical. This vulnerability affects unknown code of the file drivers/tty/tty_io.c of the component Locking Handler. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2020-29660. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Linux Kernel up to 5.9.13 (Operating System). It has been declared as critical. Affected by this vulnerability is an unknown function of the file drivers/tty/tty_io.c of the component Locking Handler. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. The impact remains unknown.
The weakness was shared 12/10/2020. The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2020-29660. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/15/2020).
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org.
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: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
12/09/2020 🔍12/09/2020 🔍
12/10/2020 🔍
12/15/2020 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Not defined
CVE: CVE-2020-29660 (🔍)
GCVE (CVE): GCVE-0-2020-29660
GCVE (VulDB): GCVE-100-165949
Entry
Created: 12/10/2020 00:33Updated: 12/15/2020 11:59
Changes: 12/10/2020 00:33 (39), 12/15/2020 11:53 (2), 12/15/2020 11:59 (19)
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.