<?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 15:15:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89489 — openrisc: fix arbitrary kernel memory access via or1k_atomic syscall</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89489</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;openrisc: fix arbitrary kernel memory access via or1k_atomic syscall&lt;/p&gt;
&lt;p&gt;sys_or1k_atomic() (syscall 244 in the &amp;#34;or1k&amp;#34; ABI) takes two user
pointers, v1 and v2, and swaps the words they point to in hand-written
assembly.&lt;/p&gt;
&lt;p&gt;l.lwz   r29,0(r4)
    l.lwz   r27,0(r5)
    l.sw    0(r4),r27
    l.sw    0(r5),r29&lt;/p&gt;
&lt;p&gt;The pointers are not checked with access_ok(). The four memory
accesses also have no exception table entries.&lt;/p&gt;
&lt;p&gt;A caller passes a kernel address as either pointer, and the syscall
reads from and writes to it directly.&lt;/p&gt;
&lt;p&gt;This gives an unprivileged process a kernel read/write primitive. It
overwrites kernel data such as the sys_call_table, gaining code
execution in kernel context.&lt;/p&gt;
&lt;p&gt;Check both pointers before entering the critical section. Add fixups
for the four memory accesses so faults on valid but unmapped user
addresses return -EFAULT.&lt;/p&gt;
&lt;p&gt;[shorne@gmail.com: fix comment style]&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;openrisc: fix arbitrary kernel memory access via or1k_atomic syscall&lt;/p&gt;
&lt;p&gt;sys_or1k_atomic() (syscall 244 in the &amp;#34;or1k&amp;#34; ABI) takes two user
pointers, v1 and v2, and swaps the words they point to in hand-written
assembly.&lt;/p&gt;
&lt;p&gt;l.lwz   r29,0(r4)
    l.lwz   r27,0(r5)
    l.sw    0(r4),r27
    l.sw    0(r5),r29&lt;/p&gt;
&lt;p&gt;The pointers are not checked with access_ok(). The four memory
accesses also have no exception table entries.&lt;/p&gt;
&lt;p&gt;A caller passes a kernel address as either pointer, and the syscall
reads from and writes to it directly.&lt;/p&gt;
&lt;p&gt;This gives an unprivileged process a kernel read/write primitive. It
overwrites kernel data such as the sys_call_table, gaining code
execution in kernel context.&lt;/p&gt;
&lt;p&gt;Check both pointers before entering the critical section. Add fixups
for the four memory accesses so faults on valid but unmapped user
addresses return -EFAULT.&lt;/p&gt;
&lt;p&gt;[shorne@gmail.com: fix comment style]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89489</guid>
    </item>
  </channel>
</rss>
