<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 13:06:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90347 — arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90347</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;arm64: ptrace: Keep &amp;#39;orig_x0&amp;#39; in-sync with x0 on syscall entry&lt;/p&gt;
&lt;p&gt;Commit e057b9477232 (&amp;#34;arm64: syscall: Ensure saved x0 is kept in-sync
with tracer updates&amp;#34;) attempted to resolve a long-standing issue with
syscall entry tracing, where a tracer is able to manipulate the first
syscall argument without being subjected to seccomp or audit checking.&lt;/p&gt;
&lt;p&gt;Unfortunately, that fix was incomplete [1], as it failed to update
&amp;#39;orig_x0&amp;#39; between a tracer updating x0 during a seccomp ptrace exit
(SECCOMP_RET_TRACE) and the seccomp filter being re-evaluated.&lt;/p&gt;
&lt;p&gt;Rather than add hooks to the core seccomp code, instead move the
synchronisation code into the ptrace GPR and syscall setting code so
that &amp;#39;orig_x0&amp;#39; is kept up to date with x0 whenever we&amp;#39;re stopped on the
syscall entry path.&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;arm64: ptrace: Keep &amp;#39;orig_x0&amp;#39; in-sync with x0 on syscall entry&lt;/p&gt;
&lt;p&gt;Commit e057b9477232 (&amp;#34;arm64: syscall: Ensure saved x0 is kept in-sync
with tracer updates&amp;#34;) attempted to resolve a long-standing issue with
syscall entry tracing, where a tracer is able to manipulate the first
syscall argument without being subjected to seccomp or audit checking.&lt;/p&gt;
&lt;p&gt;Unfortunately, that fix was incomplete [1], as it failed to update
&amp;#39;orig_x0&amp;#39; between a tracer updating x0 during a seccomp ptrace exit
(SECCOMP_RET_TRACE) and the seccomp filter being re-evaluated.&lt;/p&gt;
&lt;p&gt;Rather than add hooks to the core seccomp code, instead move the
synchronisation code into the ptrace GPR and syscall setting code so
that &amp;#39;orig_x0&amp;#39; is kept up to date with x0 whenever we&amp;#39;re stopped on the
syscall entry path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90347</guid>
    </item>
  </channel>
</rss>
