<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 22:31:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93167 — csky: Fix a4/a5 restoration in syscall trace path</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93167</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;csky: Fix a4/a5 restoration in syscall trace path&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This is visible with mmap2(), which takes six arguments. A small
PTRACE_SYSCALL reproducer opens a file and maps one page with:&lt;/p&gt;
&lt;p&gt;mmap(NULL, 4096, PROT_READ | PROT_EXEC, MAP_PRIVATE, fd, 0)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix the trace path by loading a4/a5 from pt_regs before changing sp.&lt;/p&gt;
&lt;p&gt;Tested on: ck860f, linux-4.19.15, C-SKY abiv2&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;csky: Fix a4/a5 restoration in syscall trace path&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This is visible with mmap2(), which takes six arguments. A small
PTRACE_SYSCALL reproducer opens a file and maps one page with:&lt;/p&gt;
&lt;p&gt;mmap(NULL, 4096, PROT_READ | PROT_EXEC, MAP_PRIVATE, fd, 0)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Fix the trace path by loading a4/a5 from pt_regs before changing sp.&lt;/p&gt;
&lt;p&gt;Tested on: ck860f, linux-4.19.15, C-SKY abiv2&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93167</guid>
    </item>
  </channel>
</rss>
