CVE-2026-68185
Received Received - Intake

Linux Kernel Memory Profiling Boot Failure

Publication date: 2026-08-10

Last updated on: 2026-08-10

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-10
Last Modified
2026-08-10
Generated
2026-08-10
AI Q&A
2026-08-10
EPSS Evaluated
N/A
NVD
CVE-2026-68185
EUVD
EUVD-2026-55286

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability where enabling memory profiling and then disabling it via a boot parameter causes the kernel to fail booting. The issue arises because a critical initialization function, jump_label_init(), must run before parsing early boot parameters. Without this fix, early parameter handlers cannot properly modify static keys, leading to boot failure.

Detection Guidance

This vulnerability is specific to the Linux kernel configuration and boot process. Detection requires checking kernel configuration and boot parameters. Verify if CONFIG_MEM_ALLOC_PROFILING and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT are enabled in your kernel config. Check boot parameters for 'sysctl.vm.mem_profiling=0'.

Impact Analysis

If you use a Linux kernel with CONFIG_MEM_ALLOC_PROFILING and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT enabled, attempting to disable memory profiling by adding 'sysctl.vm.mem_profiling=0' to boot parameters will cause the system to fail to boot. This disrupts normal operation and requires a workaround or kernel update.

Mitigation Strategies

Update your Linux kernel to a patched version that includes the fix. Avoid using the 'sysctl.vm.mem_profiling=0' boot parameter if CONFIG_MEM_ALLOC_PROFILING is enabled. Reconfigure the kernel to disable MEM_ALLOC_PROFILING if not needed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-68185. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart