CVE-2026-68185: LoongArch: Move jump_label_init() before parse_early_param()
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Move jumplabelinit() before parseearlyparam()
When enabling both CONFIGMEMALLOCPROFILING=y and CONFIGMEMALLOCPROFILINGENABLEDBYDEFAULT=y, then diabling memory profiling by adding the boot parameter 'sysctl.vm.memprofiling=0' will cause the kernel failed to boot.
After analysis, this is because jumplabelinit() must be called before parseearlyparam(), the early param handlers may modify static keys by staticbranchenable/disable().
Fix this by moving jumplabelinit() to before parseearlyparam(). The solution is similar to other architectures.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch LoongArch: Move jump_label_init() before parse_early_param() - Configuration
If you have CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, prevent the boot-time static-key modifications by disabling mem profiling via the boot parameter 'sysctl.vm.mem_profiling=0'.
Linux kernel boot parameters (sysctl) sysctl.vm.mem_profiling = 0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68185?
CVE-2026-68185 is assessed with a risk rating of 22.
How do I fix CVE-2026-68185?
To fix CVE-2026-68185, ensure that jump_label_init() is called before parse_early_param() when configuring your Linux kernel.
What systems are affected by CVE-2026-68185?
CVE-2026-68185 affects systems running the Linux kernel with LoongArch architecture and specific memory profiling configurations.
What are the implications of CVE-2026-68185?
The implications of CVE-2026-68185 include potential instability or unexpected behavior during memory profiling operations.
When was CVE-2026-68185 published?
CVE-2026-68185 was published on August 10, 2026.