CVE-2026-68185

LoongArch: Move jump_label_init() before parse_early_param()

Published Aug 10, 2026 CVSS n/a EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

In the LoongArch implementation of the Linux kernel, the function that initializes branch prediction keys, jump_label_init(), was executed after early parameter parsing. When both memory‑allocation profiling features are enabled during compilation and a boot parameter disables profiling, the kernel aborts during initialization, preventing the system from booting. This improper ordering is a flaw that leads to a complete denial of service by causing the kernel to fail to start.

Affected Systems

The vulnerability affects the Linux kernel for the LoongArch architecture. Any kernel build that includes CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, with the jump_label_init() call positioned after parse_early_param(), is susceptible. No specific releases are enumerated, so all kernels containing this ordering prior to the patch are potentially impacted.

Risk and Exploitability

The EPSS score for this vulnerability is <1%; it is also not listed in the CISA KEV catalog. The attack vector is not explicitly described in the input; the likely vector is that an attacker must be able to modify the boot configuration to supply the sysctl.vm.mem_profiling=0 boot parameter, such as by controlling the boot loader or firmware. Based on the description, it is inferred that once this parameter is applied to a vulnerable kernel, boot failure occurs deterministically. The impact is a full denial of service to any affected system that requires booting.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a release where jump_label_init() is executed before parse_early_param()
  • If an update is not immediately possible, disable the CONFIG_MEM_ALLOC_PROFILING option or set CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT to n in the kernel configuration
  • Avoid supplying the sysctl.vm.mem_profiling=0 boot parameter on a vulnerable kernel until the patch has been applied

Generated by OpenCVE AI on August 13, 2026 at 07:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
History
Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
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.
Title LoongArch: Move jump_label_init() before parse_early_param()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-628

    Function Call with Incorrectly Specified Arguments

  • CWE-665

    Improper Initialization

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:28 PM
Reserved
Jul 30, 2026, 9:28 AM
Status
Received
Published
Aug 10, 2026, 1:20 PM
Modified
Oct 30, 2026, 1:19 PM
Severity
Moderate
Public date
Aug 10, 2026, 12:00 AM