CVE-2026-68185: LoongArch: Move jump_label_init() before parse_early_param()

From: Greg Kroah-Hartman <[email protected]>

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2026-68185 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.12.101 with commit 4b40e590efb350c54480d7e883f054d3609a94c6
	Fixed in 6.18.42 with commit 38b025fcdc45bdf5140a5726a1fbb2e694ea047b
	Fixed in 7.1.6 with commit 881e9f3c4e117b100880b1c5de3a0da8e455a78f
	Fixed in 7.2-rc5 with commit ea68d444a658783234a06f05414e41cf93a18fb2

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-68185
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	arch/loongarch/kernel/setup.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/4b40e590efb350c54480d7e883f054d3609a94c6
	https://git.kernel.org/stable/c/38b025fcdc45bdf5140a5726a1fbb2e694ea047b
	https://git.kernel.org/stable/c/881e9f3c4e117b100880b1c5de3a0da8e455a78f
	https://git.kernel.org/stable/c/ea68d444a658783234a06f05414e41cf93a18fb2