LoongArch: Move jump_label_init() before parse_early_param()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 628c3bb40e9a8cefc0a6fde28b7b66bfe46d1dc2 · < ea68d444a658783234a06f05414e41cf93a18fb2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Move jump_label_init() before parse_early_param()
When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter 'sysctl.vm.mem_profiling=0' will cause the kernel failed to boot.
After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable().
Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.
From the CVE record · Linux
On LoongArch, the Linux kernel can fail to boot when memory allocation profiling and profiling by default are enabled, then disabled with the boot parameter `sysctl.vm.mem_profiling=0`. The input describes a boot-time failure, not an attacker-triggered network or local exploit; authentication and user interaction are not specified.
Engineers running Linux kernels on LoongArch with both `CONFIG_MEM_ALLOC_PROFILING=y` and `CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y` should check their systems; affected versions are not specified.