Bug 1224563 (CVE-2024-35987)

Summary: VUL-0: CVE-2024-35987: kernel: riscv: Fix loading 64-bit NOMMU kernels past the start of RAM
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Security Team bot <security-team>
Status: RESOLVED INVALID QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P3 - Medium CC: gianluca.gabrielli, jlee, security-team, thomas.leroy
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/406716/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-35987:5.5:(AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-05-20 14:37:21 UTC
In the Linux kernel, the following vulnerability has been resolved:

riscv: Fix loading 64-bit NOMMU kernels past the start of RAM

commit 3335068f8721 ("riscv: Use PUD/P4D/PGD pages for the linear
mapping") added logic to allow using RAM below the kernel load address.
However, this does not work for NOMMU, where PAGE_OFFSET is fixed to the
kernel load address. Since that range of memory corresponds to PFNs
below ARCH_PFN_OFFSET, mm initialization runs off the beginning of
mem_map and corrupts adjacent kernel memory. Fix this by restoring the
previous behavior for NOMMU kernels.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35987
https://www.cve.org/CVERecord?id=CVE-2024-35987
https://git.kernel.org/stable/c/aea702dde7e9876fb00571a2602f25130847bf0f
https://git.kernel.org/stable/c/b008e327fa570aca210f98c817757649bae56694
https://git.kernel.org/stable/c/ea6628e4e2353978af7e3b4ad4fdaab6149acf3d
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-35987.mbox
Comment 1 Joey Lee 2024-05-21 09:26:33 UTC
https://www.suse.com/security/cve/CVE-2024-35987.html
cvss 5.5
Comment 2 Joey Lee 2024-05-22 15:48:58 UTC
We do NOT official support RISCV. Should we handle this CVE issue?
Comment 3 Thomas Leroy 2024-05-28 09:46:32 UTC
riscv unsupported, closing