LoongArch: Fix address space mismatch in kexec command line lookup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 · < 485ed44db5694d8d2e5027f63ad608e705286f30| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Fix address space mismatch in kexec command line lookup
When searching the loaded segments for the "kexec" command line marker, the kexec_load(2) path (file_mode == 0) passes the user-space segment buffer straight to strncmp() through a bogus (char __user *) cast. This dereferences a user pointer in kernel context, which is wrong and is flagged by sparse:
arch/loongarch/kernel/machine_kexec.c:84:51: sparse: incorrect type in argument 2 (different address spaces) @@ expected char const * @@ got char [noderef] __user *
Here copy the marker-sized prefix of each segment into a small on-stack buffer with copy_from_user() before comparing, and skip segments that fault. The subsequent copy_from_user() that stages the full command line into the safe area is left unchanged.
From the CVE record · Linux
The LoongArch kernel kexec_load(2) path incorrectly dereferences a user-space segment buffer while looking for a command-line marker. This occurs on the non-file-mode path; the input does not specify an attacker outcome, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels on LoongArch should check their kernel versions; affected versions are not specified.