Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-26893 | First vendor Publication | 2024-04-17 |
Vendor | Cve | Last vendor Modification | 2025-01-27 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 5.5 | ||
Base Score | 5.5 | Environmental Score | 5.5 |
impact SubScore | 3.6 | Temporal Score | 5.5 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | None | 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: firmware: arm_scmi: Fix double free in SMC transport cleanup path When the generic SCMI code tears down a channel, it calls the chan_free callback function, defined by each transport. Since multiple protocols might share the same transport_info member, chan_free() might want to clean up the same member multiple times within the given SCMI transport implementation. In this case, it is SMC transport. This will lead to a NULL pointer dereference at the second time: | scmi_protocol scmi_dev.1: Enabled polling mode TX channel - prot_id:16 Simply check for the struct pointer being NULL before trying to access its members, to avoid this situation. This was found when a transport doesn't really work (for instance no SMC service), the probe routines then tries to clean up, and triggers a crash. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26893 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-415 | Double Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:29:54 |
|
2025-06-25 12:30:04 |
|
2025-06-24 02:34:23 |
|
2025-05-27 02:36:34 |
|
2025-03-29 03:35:33 |
|
2025-03-28 13:41:36 |
|
2025-03-28 03:14:36 |
|
2025-03-19 03:10:09 |
|
2025-03-18 03:22:50 |
|
2025-03-14 03:10:25 |
|
2025-03-06 14:06:39 |
|
2025-02-22 03:20:17 |
|
2025-01-27 21:20:46 |
|
2024-11-25 09:26:04 |
|
2024-04-17 17:28:32 |
|