CVE-2026-93167: Linux kernel · csky: Fix a4/a5 restoration in syscall trace path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e71a3dc5b8d2ea4d9cfbdb135d6b7777de84212e : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e71a3dc5b8d2ea4d9cfbdb135d6b7777de84212e, e9ae8e86eed68bea5d2670eadf61938a43bd2263, abb81e5ce7d995baa41556b8125fa59e28ba3be8 +7
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 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– |
AI-suggested
A fix is available and included in Linux kernel versions 5.5, 5.7, and related commits. Users running affected kernel versions (>=5.4.47 <5.5, >=5.6.19 <5.7, =5.7) should upgrade to a fixed version to resolve the issue. No additional mitigation is required beyond applying the official kernel update.
Description
A vulnerability in the Linux kernel's C-SKY architecture syscall trace path caused incorrect restoration of the 5th and 6th syscall arguments during ptrace syscall tracing. This led to corrupted syscall arguments for traced syscalls using these parameters, such as mmap2(), causing failures in traced processes. The issue was fixed by correcting the order of loading these arguments from pt_regs before adjusting the stack pointer.
References
- git.kernel.org/stable/c/e9ae8e86eed68bea5d2670eadf61938a43bd2263 (opens in a new tab)
- git.kernel.org/stable/c/64e3ec7a71d3b715e2567f19f64207f04999bb0c (opens in a new tab)
- git.kernel.org/stable/c/863fa63fd1491f201ac819f805a8db98d2a32c3d (opens in a new tab)
- git.kernel.org/stable/c/e71a3dc5b8d2ea4d9cfbdb135d6b7777de84212e (opens in a new tab)
- git.kernel.org/stable/c/31c81b376e5f058c7f2c94f69719cf7caec2fc3f (opens in a new tab)
- git.kernel.org/stable/c/a776afa89424570bfa637ebf812ca281a5732904 (opens in a new tab)
- git.kernel.org/stable/c/343aa5275484d627c921a42e8e115cae366be5de (opens in a new tab)
- git.kernel.org/stable/c/abb81e5ce7d995baa41556b8125fa59e28ba3be8 (opens in a new tab)