CVE-2024-38667
Last modified
CVE-2024-38667 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 6.1.93 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.33 | — |
| Linux | Linux Kernel | >= 6.7, < 6.9.4 | — |
| Linux | Linux Kernel | 6.10 | Rc1 |
References
- https://git.kernel.org/stable/c/0c1f28c32a194303da630fca89481334b9547b80Mailing List, Patch
- https://git.kernel.org/stable/c/0c1f28c32a194303da630fca89481334b9547b80Mailing List, Patch
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-38667?
How severe is CVE-2024-38667?
How do I fix CVE-2024-38667?
Are you affected by CVE-2024-38667?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
