CVE-2026-93167

csky: Fix a4/a5 restoration in syscall trace path

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: csky: Fix a4/a5 restoration in syscall trace path The syscall trace path reloads syscall arguments from pt_regs before calling the syscall handler. On C-SKY ABIv2, the 5th and 6th syscall arguments are prepared as stack arguments before invoking syscallid. The current code adjusts sp before loading LSAVE_A4 and LSAVE_A5. Since those offsets are relative to the original pt_regs base, loading them after changing sp fetches the wrong slots. As a result, traced syscalls that use the 5th or 6th argument may receive corrupted arguments. This is visible with mmap2(), which takes six arguments. A small PTRACE_SYSCALL reproducer opens a file and maps one page with: mmap(NULL, 4096, PROT_READ | PROT_EXEC, MAP_PRIVATE, fd, 0) Before the fix, the traced child fails the mmap and exits with 12. After the fix, the mapping succeeds and the child exits with 0. Fix the trace path by loading a4/a5 from pt_regs before changing sp. Tested on: ck860f, linux-4.19.15, C-SKY abiv2

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

108681048cf728a8570e036c34ebd7daa43133b43a5837c692918c229baf63fe7950965d27c48ac25.4.475.6.195.7e0bbb53843b5fdfe464b099217e3b9d97e8a75d7
Vendor states this is fixed in 31c81b376e5f058c7f2c94f69719cf7caec2fc3f (fixed)
Vendor states this is fixed in 343aa5275484d627c921a42e8e115cae366be5de (fixed)
Vendor states this is fixed in 64e3ec7a71d3b715e2567f19f64207f04999bb0c (fixed)
Vendor states this is fixed in 863fa63fd1491f201ac819f805a8db98d2a32c3d (fixed)
Vendor states this is fixed in a776afa89424570bfa637ebf812ca281a5732904 (fixed)
Vendor states this is fixed in abb81e5ce7d995baa41556b8125fa59e28ba3be8 (fixed)
Vendor states this is fixed in e71a3dc5b8d2ea4d9cfbdb135d6b7777de84212e (fixed)
Vendor states this is fixed in e9ae8e86eed68bea5d2670eadf61938a43bd2263 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card