Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-57801 | First vendor Publication | 2025-01-15 |
| Vendor | Cve | Last vendor Modification | 2025-02-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: net/mlx5e: Skip restore TC rules for vport rep without loaded flag During driver unload, unregister_netdev is called after unloading vport rep. So, the mlx5e_rep_priv is already freed while trying to get rpriv->netdev, or walk rpriv->tc_ht, which results in use-after-free. So add the checking to make sure access the data of vport rep which is still loaded. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57801 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-416 | Use After Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-07-14 12:38:51 |
|
| 2025-06-26 02:38:49 |
|
| 2025-06-25 12:36:51 |
|
| 2025-06-24 02:43:25 |
|
| 2025-05-27 02:48:53 |
|
| 2025-03-29 03:44:44 |
|
| 2025-03-28 13:47:59 |
|
| 2025-03-28 03:22:34 |
|
| 2025-03-25 03:28:31 |
|
| 2025-03-19 03:17:21 |
|
| 2025-03-18 03:30:20 |
|
| 2025-03-14 03:17:26 |
|
| 2025-03-06 14:14:00 |
|
| 2025-02-22 03:27:31 |
|
| 2025-02-11 21:20:48 |
|
| 2025-01-21 21:20:42 |
|
| 2025-01-15 17:20:30 |
|
