CVE-2026-68435: Linux kernel · LoongArch: Fix address space mismatch in kexec command line lookup
Source GCVE Database
Not known to be exploited · fixed in eaa908d8d523b0ab75dab5ebd6662e70af5e5d7e : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in eaa908d8d523b0ab75dab5ebd6662e70af5e5d7e, a94d6726ec8680a2b0c453fc782a543f68a1ea06, 485ed44db5694d8d2e5027f63ad608e705286f30 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel source code for the LoongArch architecture that properly copies user-space data into kernel space before comparison, preventing address space mismatches. Users should update their Linux kernel to a version that includes this fix once available.
Description
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix address space mismatch in kexec command line lookup When searching the loaded segments for the "kexec" command line marker, the kexec_load(2) path (file_mode == 0) passes the user-space segment buffer straight to strncmp() through a bogus (char __user *) cast. This dereferences a user pointer in kernel context, which is wrong and is flagged by sparse: arch/loongarch/kernel/machine_kexec.c:84:51: sparse: incorrect type in argument 2 (different address spaces) @@ expected char const * @@ got char [noderef] __user * Here copy the marker-sized prefix of each segment into a small on-stack buffer with copy_from_user() before comparing, and skip segments that fault. The subsequent copy_from_user() that stages the full command line into the safe area is left unchanged.
References
- nvd.nist.gov/vuln/detail/CVE-2026-68435 (opens in a new tab)
- git.kernel.org/stable/c/485ed44db5694d8d2e5027f63ad608e705286f30 (opens in a new tab)
- git.kernel.org/stable/c/7a54e0cbaad4a5a09e7cc7a4f05d181048e98ca7 (opens in a new tab)
- git.kernel.org/stable/c/a94d6726ec8680a2b0c453fc782a543f68a1ea06 (opens in a new tab)
- ubuntu.com/security/CVE-2026-68435 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-68435 (opens in a new tab)
- git.kernel.org/stable/c/3b71f51fa3a247921408879eab2ddee82da8a980 (opens in a new tab)
- git.kernel.org/stable/c/eaa908d8d523b0ab75dab5ebd6662e70af5e5d7e (opens in a new tab)