Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-43815 | First vendor Publication | 2024-08-17 |
Vendor | Cve | Last vendor Modification | 2025-02-03 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.1 | ||
Base Score | 7.1 | Environmental Score | 7.1 |
impact SubScore | 5.2 | Temporal Score | 7.1 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
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: crypto: mxs-dcp - Ensure payload is zero when using key slot We could leak stack memory through the payload field when running AES with a key from one of the hardware's key slots. Fix this by ensuring the payload field is set to 0 in such cases. This does not affect the common use case when the key is supplied from main memory via the descriptor payload. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43815 |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2025-06-26 02:33:57 |
|
2025-06-25 12:32:48 |
|
2025-06-24 02:38:36 |
|
2025-05-27 02:42:58 |
|
2025-03-29 03:39:28 |
|
2025-03-28 13:44:09 |
|
2025-03-28 03:17:45 |
|
2025-03-19 03:13:08 |
|
2025-03-18 03:26:03 |
|
2025-03-14 03:13:21 |
|
2025-03-06 14:09:53 |
|
2025-02-22 03:23:24 |
|
2025-02-03 21:21:00 |
|
2024-08-19 17:27:25 |
|
2024-08-17 17:27:28 |
|