<?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 22:14:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04559</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04559</link>
      <description>bdu:2026-04559</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04559</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0587 — 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-0587</link>
      <description>certfr-2025-avi-0587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</guid>
    </item>
    <item>
      <title>EUVD-2026-310952</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310952</link>
      <description>EUVD-2026-310952</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310952</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50008</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50008</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes&lt;/p&gt;
&lt;p&gt;The assumption in __disable_kprobe() is wrong, and it could try to disarm
an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can
easily reproduce this issue.&lt;/p&gt;
&lt;p&gt;1. Write 0 to /sys/kernel/debug/kprobes/enabled.&lt;/p&gt;
&lt;p&gt;# echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;2. Run execsnoop.  At this time, one kprobe is disabled.&lt;/p&gt;
&lt;p&gt;# /usr/share/bcc/tools/execsnoop &amp;amp;
  [1] 2460
  PCOMM            PID    PPID   RET ARGS&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes
   kprobes_all_disarmed to false but does not arm the disabled kprobe.&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the
   disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().&lt;/p&gt;
&lt;p&gt;# fg
  /usr/share/bcc/tools/execsnoop
  ^C&lt;/p&gt;
&lt;p&gt;Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses
some cleanups and leaves the aggregated kprobe in the hash table.  Then,
__unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an
infinite loop like this.&lt;/p&gt;
&lt;p&gt;aggr…&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;kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes&lt;/p&gt;
&lt;p&gt;The assumption in __disable_kprobe() is wrong, and it could try to disarm
an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can
easily reproduce this issue.&lt;/p&gt;
&lt;p&gt;1. Write 0 to /sys/kernel/debug/kprobes/enabled.&lt;/p&gt;
&lt;p&gt;# echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;2. Run execsnoop.  At this time, one kprobe is disabled.&lt;/p&gt;
&lt;p&gt;# /usr/share/bcc/tools/execsnoop &amp;amp;
  [1] 2460
  PCOMM            PID    PPID   RET ARGS&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes
   kprobes_all_disarmed to false but does not arm the disabled kprobe.&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the
   disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().&lt;/p&gt;
&lt;p&gt;# fg
  /usr/share/bcc/tools/execsnoop
  ^C&lt;/p&gt;
&lt;p&gt;Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses
some cleanups and leaves the aggregated kprobe in the hash table.  Then,
__unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an
infinite loop like this.&lt;/p&gt;
&lt;p&gt;aggr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50008</guid>
    </item>
    <item>
      <title>GHSA-q44m-58pc-8rr7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q44m-58pc-8rr7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes&lt;/p&gt;
&lt;p&gt;The assumption in __disable_kprobe() is wrong, and it could try to disarm
an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can
easily reproduce this issue.&lt;/p&gt;
&lt;p&gt;1. Write 0 to /sys/kernel/debug/kprobes/enabled.&lt;/p&gt;
&lt;p&gt;# echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;2. Run execsnoop.  At this time, one kprobe is disabled.&lt;/p&gt;
&lt;p&gt;# /usr/share/bcc/tools/execsnoop &amp;amp;
  [1] 2460
  PCOMM            PID    PPID   RET ARGS&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes
   kprobes_all_disarmed to false but does not arm the disabled kprobe.&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the
   disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().&lt;/p&gt;
&lt;p&gt;# fg
  /usr/share/bcc/tools/execsnoop
  ^C&lt;/p&gt;
&lt;p&gt;Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses
some cleanups and leaves the aggregated kprobe in the hash table.  Then,
__unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an
infinite loop like this.&lt;/p&gt;
&lt;p&gt;aggr…&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;kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes&lt;/p&gt;
&lt;p&gt;The assumption in __disable_kprobe() is wrong, and it could try to disarm
an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can
easily reproduce this issue.&lt;/p&gt;
&lt;p&gt;1. Write 0 to /sys/kernel/debug/kprobes/enabled.&lt;/p&gt;
&lt;p&gt;# echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;2. Run execsnoop.  At this time, one kprobe is disabled.&lt;/p&gt;
&lt;p&gt;# /usr/share/bcc/tools/execsnoop &amp;amp;
  [1] 2460
  PCOMM            PID    PPID   RET ARGS&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes
   kprobes_all_disarmed to false but does not arm the disabled kprobe.&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled&lt;/p&gt;
&lt;p&gt;# cat /sys/kernel/debug/kprobes/list
  ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]
  ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE]&lt;/p&gt;
&lt;p&gt;4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the
   disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().&lt;/p&gt;
&lt;p&gt;# fg
  /usr/share/bcc/tools/execsnoop
  ^C&lt;/p&gt;
&lt;p&gt;Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses
some cleanups and leaves the aggregated kprobe in the hash table.  Then,
__unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an
infinite loop like this.&lt;/p&gt;
&lt;p&gt;aggr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q44m-58pc-8rr7</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02264-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02264-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:02264-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50008</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50008</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 145 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes The assumption in __disable_kprobe() is wrong, and it could try to disarm an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can easily reproduce this issue. 1. Write 0 to /sys/kernel/debug/kprobes/enabled.   # echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled 2. Run execsnoop.  At this time, one kprobe is disabled.   # /usr/share/bcc/tools/execsnoop &amp;amp;   [1] 2460   PCOMM            PID    PPID   RET ARGS   # cat /sys/kernel/debug/kprobes/list   ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]   ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE] 3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes    kprobes_all_disarmed to false but does not arm the disabled kprobe.   # echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled   # cat /sys/kernel/debug/kprobes/list   ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]   ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE] 4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the    disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().   # fg   /usr/share/bcc/tools/execsnoop   ^C Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses some cleanups and leaves the aggregated kprobe in the hash table.  Then, __unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an infinite loop like this.   aggregated kprobe.…&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:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 145 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: kprobes: don&amp;#39;t call disarm_kprobe() for disabled kprobes The assumption in __disable_kprobe() is wrong, and it could try to disarm an already disarmed kprobe and fire the WARN_ONCE() below. [0]  We can easily reproduce this issue. 1. Write 0 to /sys/kernel/debug/kprobes/enabled.   # echo 0 &amp;gt; /sys/kernel/debug/kprobes/enabled 2. Run execsnoop.  At this time, one kprobe is disabled.   # /usr/share/bcc/tools/execsnoop &amp;amp;   [1] 2460   PCOMM            PID    PPID   RET ARGS   # cat /sys/kernel/debug/kprobes/list   ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]   ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE] 3. Write 1 to /sys/kernel/debug/kprobes/enabled, which changes    kprobes_all_disarmed to false but does not arm the disabled kprobe.   # echo 1 &amp;gt; /sys/kernel/debug/kprobes/enabled   # cat /sys/kernel/debug/kprobes/list   ffffffff91345650  r  __x64_sys_execve+0x0    [FTRACE]   ffffffff91345650  k  __x64_sys_execve+0x0    [DISABLED][FTRACE] 4. Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the    disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().   # fg   /usr/share/bcc/tools/execsnoop   ^C Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses some cleanups and leaves the aggregated kprobe in the hash table.  Then, __unregister_trace_kprobe() initialises tk-&amp;gt;rp.kp.list and creates an infinite loop like this.   aggregated kprobe.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50008</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
