Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-38667 | First vendor Publication | 2024-06-24 |
| Vendor | Cve | Last vendor Modification | 2025-05-30 |
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: riscv: prevent pt_regs corruption for secondary idle threads Top of the kernel thread stack should be reserved for pt_regs. However this is not the case for the idle threads of the secondary boot harts. Their stacks overlap with their pt_regs, so both may get corrupted. Similar issue has been fixed for the primary hart, see c7cdd96eca28 ("riscv: prevent stack corruption by reserving task_pt_regs(p) early"). However that fix was not propagated to the secondary harts. The problem has been noticed in some CPU hotplug tests with V enabled. The function smp_callin stored several registers on stack, corrupting top of pt_regs structure including status field. As a result, kernel attempted to save or restore inexistent V context. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38667 |
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-06-26 02:32:18 |
|
| 2025-06-25 12:31:44 |
|
| 2025-06-24 02:36:57 |
|
| 2025-05-31 00:20:47 |
|
| 2025-05-27 02:41:24 |
|
| 2025-03-29 03:37:41 |
|
| 2025-03-28 13:43:08 |
|
| 2025-03-28 03:16:21 |
|
| 2025-03-19 03:11:46 |
|
| 2025-03-18 03:24:38 |
|
| 2025-03-14 03:12:01 |
|
| 2025-03-06 14:08:24 |
|
| 2025-02-22 03:21:50 |
|
| 2025-01-08 03:03:17 |
|
| 2025-01-07 03:02:50 |
|
| 2024-12-25 03:01:28 |
|
| 2024-12-12 03:04:25 |
|
| 2024-11-25 09:24:29 |
|
| 2024-11-22 21:23:28 |
|
| 2024-11-21 21:23:05 |
|
| 2024-11-20 02:58:05 |
|
| 2024-11-14 02:58:23 |
|
| 2024-11-09 02:58:24 |
|
| 2024-10-26 02:55:48 |
|
| 2024-10-25 02:57:43 |
|
| 2024-10-23 02:56:56 |
|
| 2024-10-03 02:52:16 |
|
| 2024-10-02 02:50:40 |
|
| 2024-09-15 02:48:30 |
|
| 2024-09-12 02:48:04 |
|
| 2024-09-07 02:47:04 |
|
| 2024-09-06 02:46:16 |
|
| 2024-09-04 02:49:29 |
|
| 2024-08-22 02:47:30 |
|
| 2024-08-02 13:56:32 |
|
| 2024-08-02 01:35:46 |
|
| 2024-06-26 17:27:25 |
|
| 2024-06-25 00:27:27 |
|
| 2024-06-24 21:27:25 |
|
