Bug 1226952 (CVE-2024-38667)

Summary: VUL-0: CVE-2024-38667: kernel: riscv: prevent pt_regs corruption for secondary idle threads
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Kernel Bugs <kernel-bugs>
Status: RESOLVED INVALID QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P5 - None CC: camila.matos
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/411972/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-38667:6.4:(AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-06-25 11:39:55 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-38667
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-38667.mbox
https://git.kernel.org/stable/c/ea22d4195cca13d5fdbc4d6555a2dfb8a7867a9e
https://git.kernel.org/stable/c/3090c06d50eaa91317f84bf3eac4c265e6cb8d44
https://git.kernel.org/stable/c/0c1f28c32a194303da630fca89481334b9547b80
https://git.kernel.org/stable/c/a638b0461b58aa3205cd9d5f14d6f703d795b4af
https://www.cve.org/CVERecord?id=CVE-2024-38667