Linux Kernel up to 5.1.5 net/ipv4/ip_sockglue.c ip_ra_control null pointer dereference ⚔ [Disputed]

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.4 | $0-$5k | 0.00 |
A vulnerability was found in Linux Kernel up to 5.1.5 (Operating System). It has been declared as critical. Affected by this vulnerability is the function ip_ra_control
of the file net/ipv4/ip_sockglue.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in ip_ra_control in net/ipv4/ip_sockglue.c in the Linux kernel through 5.1.5. There is an unchecked kmalloc of new_ra, which might allow an attacker to cause a denial of service (NULL pointer dereference and system crash).
The weakness was published 05/25/2019 (Website). It is possible to read the advisory at lkml.org. This vulnerability is known as CVE-2019-12381 since 05/27/2019. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. Responsible for the vulnerability is the following code:
new_ra = on ? kmalloc(sizeof(*new_ra), GFP_KERNEL) : NULL; mutex_lock(&net->ipv4.ra_mutex); for (rap = &net->ipv4.ra_chain;
The real existence of this vulnerability is still doubted at the moment.
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:
new_ra = on ? kmalloc(sizeof(*new_ra), GFP_KERNEL) : NULL; if (on && !new_ra) return -ENOMEM; mutex_lock(&net->ipv4.ra_mutex); for (rap = &net->ipv4.ra_chain;
Similar entries are available at VDB-135656, VDB-135654, VDB-135653 and VDB-135652. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
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/25/2019 🔍05/25/2019 🔍
05/27/2019 🔍
05/28/2019 🔍
08/05/2024 🔍
Sources
Vendor: kernel.orgAdvisory: FEDORA-2019-7ec378191e
Status: Not defined
Disputed: 🔍
CVE: CVE-2019-12381 (🔍)
GCVE (CVE): GCVE-0-2019-12381
GCVE (VulDB): GCVE-100-135655
SecurityFocus: 108473
See also: 🔍
Entry
Created: 05/28/2019 10:03 AMUpdated: 08/05/2024 02:31 AM
Changes: 05/28/2019 10:03 AM (46), 06/16/2020 06:06 PM (18), 09/24/2023 02:42 PM (5), 08/05/2024 02:31 AM (26)
Complete: 🔍
Cache ID: 18:630:40
No comments yet. Languages: en.
Please log in to comment.