Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-45020 | First vendor Publication | 2024-09-11 |
Vendor | Cve | Last vendor Modification | 2024-09-13 |
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: bpf: Fix a kernel verifier crash in stacksafe() Daniel Hodges reported a kernel verifier crash when playing with sched-ext. Further investigation shows that the crash is due to invalid memory access in stacksafe(). More specifically, it is the following code: if (exact != NOT_EXACT && The 'i' iterates old->allocated_stack. If cur->allocated_stack < old->allocated_stack the out-of-bound access will happen. To fix the issue add 'i >= cur->allocated_stack' check such that if the condition is true, stacksafe() should fail. Otherwise, cur->stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45020 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-787 | Out-of-bounds Write (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-01-08 03:05:00 |
|
2025-01-07 03:04:33 |
|
2024-12-25 03:03:11 |
|
2024-12-12 03:06:07 |
|
2024-11-23 03:03:08 |
|
2024-11-22 03:01:18 |
|
2024-11-20 02:59:38 |
|
2024-11-14 02:59:57 |
|
2024-11-09 02:59:57 |
|
2024-10-26 02:57:20 |
|
2024-10-25 02:59:13 |
|
2024-10-23 02:58:24 |
|
2024-10-03 02:53:36 |
|
2024-10-02 02:52:00 |
|
2024-09-14 21:29:46 |
|
2024-09-13 21:27:57 |
|
2024-09-11 21:27:24 |
|