{
  "id": "CVE-2026-90347",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-90347",
  "published_at": "2026-09-17T16:08:56.232Z",
  "title": "arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 8.4,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry\n\nCommit e057b9477232 (\"arm64: syscall: Ensure saved x0 is kept in-sync\nwith tracer updates\") attempted to resolve a long-standing issue with\nsyscall entry tracing, where a tracer is able to manipulate the first\nsyscall argument without being subjected to seccomp or audit checking.\n\nUnfortunately, that fix was incomplete [1], as it failed to update\n'orig_x0' between a tracer updating x0 during a seccomp ptrace exit\n(SECCOMP_RET_TRACE) and the seccomp filter being re-evaluated.\n\nRather than add hooks to the core seccomp code, instead move the\nsynchronisation code into the ptrace GPR and syscall setting code so\nthat 'orig_x0' is kept up to date with x0 whenever we're stopped on the\nsyscall entry path.",
  "cvss_by_source": {
    "cna": 8.4
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9",
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c 332c9c1a148d0425326989c1187face8f6b2a60c",
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c ce17c651a90e242ad48df0df89b1e4cebcda5e14",
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c e9e2854fcff5733ffc607e8ecc87e0e591ab41fd",
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c f433869f23841a50455c4087d85540d5b4d37cde",
          "\u003e= a5cd110cb8369d6b37ef5ccfe56b3fa1338c9615, \u003c 88b839ce497ccb1ff92f7ae742c78dd2937ba572"
        ],
        "fixed_in": [
          "a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9",
          "332c9c1a148d0425326989c1187face8f6b2a60c",
          "ce17c651a90e242ad48df0df89b1e4cebcda5e14",
          "e9e2854fcff5733ffc607e8ecc87e0e591ab41fd",
          "f433869f23841a50455c4087d85540d5b4d37cde",
          "88b839ce497ccb1ff92f7ae742c78dd2937ba572"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "4.8"
        ],
        "fixed_in": [
          "0",
          "6.1.191",
          "6.6.160",
          "6.12.114",
          "6.18.57",
          "7.2.6",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to a9e7743b1067ea38c4ad2665d40c3c4a920ad9a9 or 332c9c1a148d0425326989c1187face8f6b2a60c or ce17c651a90e242ad48df0df89b1e4cebcda5e14 or e9e2854fcff5733ffc607e8ecc87e0e591ab41fd or f433869f23841a50455c4087d85540d5b4d37cde or 88b839ce497ccb1ff92f7ae742c78dd2937ba572 or later.",
      "Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.57 or 7.2.6 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
