{
  "id": "CVE-2026-89903",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-89903",
  "published_at": "2026-09-16T10:32:03.038Z",
  "title": "LoongArch: Do not save/restore percpu base register in rethook trampoline",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "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\nLoongArch: Do not save/restore percpu base register in rethook trampoline\n\nThe rethook trampoline saves $r21 ($u0), the percpu base, into its frame\nat entry and restores it at exit. Inbetween rethook_trampoline_handler()\nmay schedule via preempt_enable_notrace().\n\nIf the task migrates to another CPU, the frame's $r21 holds the old\nCPU's percpu base, and restoring it poisons $r21 on the new CPU. Until\nthe next user-\u003ekernel transition heals $r21, all this_cpu_*() accesses\n(runqueues, RCU per-CPU data, timer tick programming, FPU ownership)\nhit the wrong CPU's percpu area.\n\nUnder kretprobe-heavy preemptible load this can corrupt scheduler and\ntimer state: scheduling-while-atomic splats, wrong-CPU RCU warnings,\nWARN_ON_ONCE(rq != this_rq()) in nohz_balance_exit_idle(), and CPUs\nparking in the idle loop with the constant timer never re-armed (hard\nlockup). Reproduces on a Loongson-3A6000 with kretprobes on VFS paths\nplus heavy file churn (OS install / unsquashfs).\n\nBy convention $r21 always holds the current CPU's percpu base in kernel\nmode: SAVE_SOME() at exception entry reloads it only when coming from\nuser mode, and RESTORE_SOME() restores it only when returning to user\nmode; the context-switch path never writes it. Therefore the live $r21\nat trampoline exit is already correct, and nothing inbetween can change\nit legitimately (kernel C code cannot write a global register variable).\nThe same flaw existed even in the pre-rethook kretprobe trampoline since\nv6.3; it was carried over when rethook replaced it. Drop both the save\nand the restore here. Drop the restore is enough to solve the issue, and\ndrop the save is to keep the code tidy and no need to clear it.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 3f5536860086d906b01ec5ed68cf50c7edcc40af, \u003c a03b5e7483ad2c33ba5dd2adb8552e84bfee8fe2",
          "\u003e= 3f5536860086d906b01ec5ed68cf50c7edcc40af, \u003c 8f15e95b438bc6b3c9f23a33c9a0d0678ebd1dc8",
          "\u003e= 3f5536860086d906b01ec5ed68cf50c7edcc40af, \u003c 266ffc92e68593759adfe3d58f188773d32782c3",
          "\u003e= 3f5536860086d906b01ec5ed68cf50c7edcc40af, \u003c c048b0a3c0836c4b1bef4b51d355d27090bf6790",
          "\u003e= 3f5536860086d906b01ec5ed68cf50c7edcc40af, \u003c c3f2feace5e4f4b01b68b9f947b19adb4155c32e"
        ],
        "fixed_in": [
          "a03b5e7483ad2c33ba5dd2adb8552e84bfee8fe2",
          "8f15e95b438bc6b3c9f23a33c9a0d0678ebd1dc8",
          "266ffc92e68593759adfe3d58f188773d32782c3",
          "c048b0a3c0836c4b1bef4b51d355d27090bf6790",
          "c3f2feace5e4f4b01b68b9f947b19adb4155c32e"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.3"
        ],
        "fixed_in": [
          "0",
          "6.6.157",
          "6.12.110",
          "6.18.51",
          "7.2.5",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to a03b5e7483ad2c33ba5dd2adb8552e84bfee8fe2 or 8f15e95b438bc6b3c9f23a33c9a0d0678ebd1dc8 or 266ffc92e68593759adfe3d58f188773d32782c3 or c048b0a3c0836c4b1bef4b51d355d27090bf6790 or c3f2feace5e4f4b01b68b9f947b19adb4155c32e or later.",
      "Upgrade Linux to 0 or 6.6.157 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
