GHSA-4FGJ-V86W-987M

Vulnerability from github – Published: 2026-08-12 00:31 – Updated: 2026-08-12 00:31
VLAI
Details

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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-68435"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-12T00:17:43Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Fix address space mismatch in kexec command line lookup\n\nWhen searching the loaded segments for the \"kexec\" command line marker,\nthe kexec_load(2) path (file_mode == 0) passes the user-space segment\nbuffer straight to strncmp() through a bogus (char __user *) cast. This\ndereferences a user pointer in kernel context, which is wrong and is\nflagged by sparse:\n\n  arch/loongarch/kernel/machine_kexec.c:84:51: sparse: incorrect type in\n  argument 2 (different address spaces) @@ expected char const * @@ got\n  char [noderef] __user *\n\nHere copy the marker-sized prefix of each segment into a small on-stack\nbuffer with copy_from_user() before comparing, and skip segments that\nfault. The subsequent copy_from_user() that stages the full command line\ninto the safe area is left unchanged.",
  "id": "GHSA-4fgj-v86w-987m",
  "modified": "2026-08-12T00:31:12Z",
  "published": "2026-08-12T00:31:12Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68435"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/485ed44db5694d8d2e5027f63ad608e705286f30"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7a54e0cbaad4a5a09e7cc7a4f05d181048e98ca7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a94d6726ec8680a2b0c453fc782a543f68a1ea06"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…