Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-53139 | First vendor Publication | 2024-12-04 |
Vendor | Cve | Last vendor Modification | 2024-12-11 |
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: sctp: fix possible UAF in sctp_v6_available() A lockdep report [1] with CONFIG_PROVE_RCU_LIST=y hints that sctp_v6_available() is calling dev_get_by_index_rcu() and ipv6_chk_addr() without holding rcu. [1] other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 stack backtrace: Code starting with the faulting instruction =========================================== |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53139 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:43:43 |
|
2025-03-28 13:47:11 |
|
2025-03-28 03:21:30 |
|
2025-03-19 03:16:32 |
|
2025-03-18 03:29:31 |
|
2025-03-14 03:16:41 |
|
2025-03-06 14:13:14 |
|
2025-02-22 03:26:46 |
|
2025-01-08 03:07:38 |
|
2025-01-07 03:07:11 |
|
2024-12-25 03:05:46 |
|
2024-12-12 00:20:30 |
|
2024-12-11 21:20:29 |
|
2024-12-04 21:20:29 |
|