https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:29:22 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-89489 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-89489 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-367598 EUVD-2026-367598 https://cve.radiocsirt.org/vuln/euvd-2026-367598 https://cve.radiocsirt.org/vuln/fkie_cve-2026-89489 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>openrisc: fix arbitrary kernel memory access via or1k_atomic syscall</p> <p>sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly.</p> <p>l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29</p> <p>The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries.</p> <p>A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly.</p> <p>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.</p> <p>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.</p> <p>[shorne@gmail.com: fix comment style]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>openrisc: fix arbitrary kernel memory access via or1k_atomic syscall</p> <p>sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly.</p> <p>l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29</p> <p>The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries.</p> <p>A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly.</p> <p>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.</p> <p>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.</p> <p>[shorne@gmail.com: fix comment style]</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-89489 https://cve.radiocsirt.org/vuln/ghsa-9rpr-c8j9-pwgc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>openrisc: fix arbitrary kernel memory access via or1k_atomic syscall</p> <p>sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly.</p> <p>l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29</p> <p>The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries.</p> <p>A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly.</p> <p>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.</p> <p>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.</p> <p>[shorne@gmail.com: fix comment style]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>openrisc: fix arbitrary kernel memory access via or1k_atomic syscall</p> <p>sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly.</p> <p>l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29</p> <p>The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries.</p> <p>A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly.</p> <p>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.</p> <p>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.</p> <p>[shorne@gmail.com: fix comment style]</p> https://cve.radiocsirt.org/vuln/ghsa-9rpr-c8j9-pwgc https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 <p>kernel-devel-7.2.7-1.1 on GA media</p> <p>kernel-devel-7.2.7-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89489 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: openrisc: fix arbitrary kernel memory access via or1k_atomic syscall sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly. l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29 The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries. A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly. 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. 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. [shorne@gmail.com: fix comment style]</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: openrisc: fix arbitrary kernel memory access via or1k_atomic syscall sys_or1k_atomic() (syscall 244 in the &#34;or1k&#34; ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly. l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29 The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries. A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly. 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. 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. [shorne@gmail.com: fix comment style]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89489 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321