Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68435

LoongArch: Fix address space mismatch in kexec command line lookup

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.

Timeline

  1. ID reserved

    By Linux

  2. · 13 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < 742f2c0a64a7557495e831c3c112d92e308bd4ae
    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < 3b71f51fa3a247921408879eab2ddee82da8a980
    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < eaa908d8d523b0ab75dab5ebd6662e70af5e5d7e
    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < a94d6726ec8680a2b0c453fc782a543f68a1ea06
    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < 7a54e0cbaad4a5a09e7cc7a4f05d181048e98ca7
    • affected 4a03b2ac06a5bcae29371866d9d11f5bfd4c9188 – < 485ed44db5694d8d2e5027f63ad608e705286f30
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68435 badge
[![CVE-2026-68435](https://cveledger.app/badge/CVE-2026-68435.svg)](https://cveledger.app/cve/CVE-2026-68435)

Record last updated .