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

> A kernel boot failure occurs when specific memory profiling configurations are combined with a disabling boot parameter, causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-94962, BELL-CVE-2026-68185, DEBIAN-CVE-2026-68185, GHSA-pcxf-938w-xxq5, UBUNTU-CVE-2026-68185

## What is CVE-2026-68185?

CVE-2026-68185 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-68185?


## How do I fix CVE-2026-68185?

Apply the vendor's patch.

## Is CVE-2026-68185 being exploited?

There is no known exploitation of CVE-2026-68185 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68185 and fix it if it is affected.

What it is: CVE-2026-68185 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68185 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68185/ (Markdown: https://insights.sbomify.com/CVE-2026-68185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68185
- OSV: https://osv.dev/vulnerability/CVE-2026-68185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68185/
Summaries are generated and may contain mistakes; the official description above is the record.