Linux Kernel up to 5.1.5 consolemap.c con_insert_unipair resource management

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.1.5. It has been rated as problematic. Affected by this issue is the function con_insert_unipair of the file drivers/tty/vt/consolemap.c. The manipulation leads to resource management.
This vulnerability is listed as CVE-2019-12379. The attack must be carried out locally. There is no available exploit.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Linux Kernel up to 5.1.5 (Operating System) and classified as problematic. This issue affects the function con_insert_unipair of the file drivers/tty/vt/consolemap.c. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
An issue was discovered in con_insert_unipair in drivers/tty/vt/consolemap.c in the Linux kernel through 5.1.5. There is a memory leak in a certain case of an ENOMEM outcome of kmalloc.
The weakness was presented 05/24/2019 as confirmed git commit (GIT Repository). The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2019-12379 since 05/27/2019. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The following code is the reason for this vulnerability:
if (!p2) return -ENOMEM;
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. A possible mitigation has been published immediately after the disclosure of the vulnerability. The vulnerability will be addressed with the following lines of code:
if (!p2) {
kfree(p1);
p->uni_pgdir[n] = NULL;
return -ENOMEM;
}See VDB-135722, VDB-135882, VDB-135883 and VDB-136477 for similar entries. 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.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 5.5
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: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.kernel.org
Timeline
05/24/2019 🔍05/24/2019 🔍
05/27/2019 🔍
05/28/2019 🔍
08/05/2024 🔍
Sources
Vendor: kernel.orgAdvisory: FEDORA-2019-7ec378191e
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-12379 (🔍)
GCVE (CVE): GCVE-0-2019-12379
GCVE (VulDB): GCVE-100-135653
SecurityFocus: 108478
See also: 🔍
Entry
Created: 05/28/2019 10:01Updated: 08/05/2024 02:31
Changes: 05/28/2019 10:01 (64), 06/16/2020 17:52 (1), 09/24/2023 14:35 (5), 08/05/2024 02:31 (26)
Complete: 🔍
Cache ID: 216:77C: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.