<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 05:02:18 +0000</lastBuildDate>
    <item>
      <title>certfr-2025-avi-0509 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-320335</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320335</link>
      <description>EUVD-2026-320335</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320335</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49916</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49916</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rose: Fix NULL pointer dereference in rose_send_frame()&lt;/p&gt;
&lt;p&gt;The syzkaller reported an issue:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387]
CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101
Call Trace:
 &amp;lt;IRQ&amp;gt;
 rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255
 rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009
 rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111
 call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474
 expire_timers kernel/time/timer.c:1519 [inline]
 __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790
 __run_timers kernel/time/timer.c:1768 [inline]
 run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803
 __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571
 [...]
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is
called in the rose_send_frame(). It&amp;#39;s the first occurrence of the
`neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and
the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr.&lt;/p&gt;
&lt;p&gt;It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf
(&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever.
But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rose: Fix NULL pointer dereference in rose_send_frame()&lt;/p&gt;
&lt;p&gt;The syzkaller reported an issue:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387]
CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101
Call Trace:
 &amp;lt;IRQ&amp;gt;
 rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255
 rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009
 rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111
 call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474
 expire_timers kernel/time/timer.c:1519 [inline]
 __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790
 __run_timers kernel/time/timer.c:1768 [inline]
 run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803
 __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571
 [...]
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is
called in the rose_send_frame(). It&amp;#39;s the first occurrence of the
`neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and
the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr.&lt;/p&gt;
&lt;p&gt;It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf
(&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever.
But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49916</guid>
    </item>
    <item>
      <title>GHSA-7qcm-qx74-j7hr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7qcm-qx74-j7hr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rose: Fix NULL pointer dereference in rose_send_frame()&lt;/p&gt;
&lt;p&gt;The syzkaller reported an issue:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387]
CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101
Call Trace:
 &amp;lt;IRQ&amp;gt;
 rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255
 rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009
 rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111
 call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474
 expire_timers kernel/time/timer.c:1519 [inline]
 __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790
 __run_timers kernel/time/timer.c:1768 [inline]
 run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803
 __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571
 [...]
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is
called in the rose_send_frame(). It&amp;#39;s the first occurrence of the
`neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and
the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr.&lt;/p&gt;
&lt;p&gt;It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf
(&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever.
But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rose: Fix NULL pointer dereference in rose_send_frame()&lt;/p&gt;
&lt;p&gt;The syzkaller reported an issue:&lt;/p&gt;
&lt;p&gt;KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387]
CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101
Call Trace:
 &amp;lt;IRQ&amp;gt;
 rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255
 rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009
 rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111
 call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474
 expire_timers kernel/time/timer.c:1519 [inline]
 __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790
 __run_timers kernel/time/timer.c:1768 [inline]
 run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803
 __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571
 [...]
 &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is
called in the rose_send_frame(). It&amp;#39;s the first occurrence of the
`neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and
the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr.&lt;/p&gt;
&lt;p&gt;It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf
(&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever.
But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7qcm-qx74-j7hr</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49916</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49916</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rose: Fix NULL pointer dereference in rose_send_frame() The syzkaller reported an issue: KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387] CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Workqueue: rcu_gp srcu_invoke_callbacks RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101 Call Trace:  &amp;lt;IRQ&amp;gt;  rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255  rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009  rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111  call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474  expire_timers kernel/time/timer.c:1519 [inline]  __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790  __run_timers kernel/time/timer.c:1768 [inline]  run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803  __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571  [...]  &amp;lt;/IRQ&amp;gt; It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is called in the rose_send_frame(). It&amp;#39;s the first occurrence of the `neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr. It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf (&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever. But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e59d1d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rose: Fix NULL pointer dereference in rose_send_frame() The syzkaller reported an issue: KASAN: null-ptr-deref in range [0x0000000000000380-0x0000000000000387] CPU: 0 PID: 4069 Comm: kworker/0:15 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Workqueue: rcu_gp srcu_invoke_callbacks RIP: 0010:rose_send_frame+0x1dd/0x2f0 net/rose/rose_link.c:101 Call Trace:  &amp;lt;IRQ&amp;gt;  rose_transmit_clear_request+0x1d5/0x290 net/rose/rose_link.c:255  rose_rx_call_request+0x4c0/0x1bc0 net/rose/af_rose.c:1009  rose_loopback_timer+0x19e/0x590 net/rose/rose_loopback.c:111  call_timer_fn+0x1a0/0x6b0 kernel/time/timer.c:1474  expire_timers kernel/time/timer.c:1519 [inline]  __run_timers.part.0+0x674/0xa80 kernel/time/timer.c:1790  __run_timers kernel/time/timer.c:1768 [inline]  run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1803  __do_softirq+0x1d0/0x9c8 kernel/softirq.c:571  [...]  &amp;lt;/IRQ&amp;gt; It triggers NULL pointer dereference when &amp;#39;neigh-&amp;gt;dev-&amp;gt;dev_addr&amp;#39; is called in the rose_send_frame(). It&amp;#39;s the first occurrence of the `neigh` is in rose_loopback_timer() as `rose_loopback_neigh&amp;#39;, and the &amp;#39;dev&amp;#39; in &amp;#39;rose_loopback_neigh&amp;#39; is initialized sa nullptr. It had been fixed by commit 3b3fd068c56e3fbea30090859216a368398e39bf (&amp;#34;rose: Fix Null pointer dereference in rose_send_frame()&amp;#34;) ever. But it&amp;#39;s introduced by commit 3c53cd65dece47dd1f9d3a809f32e59d1d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49916</guid>
    </item>
  </channel>
</rss>
