Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-50264 | First vendor Publication | 2024-11-19 |
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: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50264 |
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:02 |
|
2025-03-28 13:46:45 |
|
2025-03-28 03:20:45 |
|
2025-03-19 03:15:56 |
|
2025-03-18 03:28:54 |
|
2025-03-14 03:16:07 |
|
2025-03-06 14:12:40 |
|
2025-02-22 03:26:13 |
|
2025-01-08 03:07:08 |
|
2025-01-07 03:06:41 |
|
2024-12-25 03:05:18 |
|
2024-12-12 00:20:53 |
|
2024-12-11 21:20:43 |
|
2024-11-23 00:22:44 |
|
2024-11-22 00:22:37 |
|
2024-11-20 03:02:02 |
|
2024-11-20 03:01:14 |
|
2024-11-20 00:20:28 |
|
2024-11-19 09:20:29 |
|