Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-36971 | First vendor Publication | 2024-06-10 |
Vendor | Cve | Last vendor Modification | 2024-08-08 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36971 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2024-10-23 02:56:37 |
|
2024-10-03 02:51:59 |
|
2024-10-02 02:50:23 |
|
2024-09-15 02:48:15 |
|
2024-09-12 02:47:48 |
|
2024-09-07 02:46:51 |
|
2024-09-06 02:46:03 |
|
2024-09-04 02:49:18 |
|
2024-08-22 02:47:21 |
|
2024-08-09 02:48:30 |
|
2024-08-09 02:47:49 |
|
2024-08-08 21:28:12 |
|
2024-08-08 09:27:37 |
|
2024-08-07 21:27:38 |
|
2024-08-02 13:56:25 |
|
2024-08-02 01:35:42 |
|
2024-07-15 13:27:34 |
|
2024-06-27 17:27:30 |
|
2024-06-16 17:27:27 |
|
2024-06-12 21:27:24 |
|
2024-06-12 17:27:25 |
|
2024-06-10 17:27:24 |
|
2024-06-10 13:27:29 |
|