<?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>Sun, 04 Oct 2026 16:48:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06685</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06685</link>
      <description>bdu:2024-06685</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06685</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-310188</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310188</link>
      <description>EUVD-2026-310188</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310188</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48848</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48848</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/osnoise: Do not unregister events twice&lt;/p&gt;
&lt;p&gt;Nicolas reported that using:&lt;/p&gt;
&lt;p&gt;# trace-cmd record -e all -M 10 -p osnoise --poll&lt;/p&gt;
&lt;p&gt;Resulted in the following kernel warning:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370
 [...]
 CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19
 RIP: 0010:tracepoint_probe_unregister+0x280/0x370
 [...]
 CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0
 Call Trace:
  &amp;lt;TASK&amp;gt;
  osnoise_workload_stop+0x36/0x90
  tracing_set_tracer+0x108/0x260
  tracing_set_trace_write+0x94/0xd0
  ? __check_object_size.part.0+0x10a/0x150
  ? selinux_file_permission+0x104/0x150
  vfs_write+0xb5/0x290
  ksys_write+0x5f/0xe0
  do_syscall_64+0x3b/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae
 RIP: 0033:0x7ff919a18127
 [...]
 ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;The warning complains about an attempt to unregister an
unregistered tracepoint.&lt;/p&gt;
&lt;p&gt;This happens on trace-cmd because it first stops tracing, and
then switches the tracer to nop. Which is equivalent to:&lt;/p&gt;
&lt;p&gt;# cd /sys/kernel/tracing/
  # echo osnoise &amp;gt; current_tracer
  # echo 0 &amp;gt; tracing_on
  # echo nop &amp;gt; current_tracer&lt;/p&gt;
&lt;p&gt;The osnoise tracer stops the workload when no trace instance
is actually collecting data. This can be caused both by
disabling tracing or disabling the tracer itself.&lt;/p&gt;
&lt;p&gt;To avoid unregistering events…&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;tracing/osnoise: Do not unregister events twice&lt;/p&gt;
&lt;p&gt;Nicolas reported that using:&lt;/p&gt;
&lt;p&gt;# trace-cmd record -e all -M 10 -p osnoise --poll&lt;/p&gt;
&lt;p&gt;Resulted in the following kernel warning:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370
 [...]
 CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19
 RIP: 0010:tracepoint_probe_unregister+0x280/0x370
 [...]
 CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0
 Call Trace:
  &amp;lt;TASK&amp;gt;
  osnoise_workload_stop+0x36/0x90
  tracing_set_tracer+0x108/0x260
  tracing_set_trace_write+0x94/0xd0
  ? __check_object_size.part.0+0x10a/0x150
  ? selinux_file_permission+0x104/0x150
  vfs_write+0xb5/0x290
  ksys_write+0x5f/0xe0
  do_syscall_64+0x3b/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae
 RIP: 0033:0x7ff919a18127
 [...]
 ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;The warning complains about an attempt to unregister an
unregistered tracepoint.&lt;/p&gt;
&lt;p&gt;This happens on trace-cmd because it first stops tracing, and
then switches the tracer to nop. Which is equivalent to:&lt;/p&gt;
&lt;p&gt;# cd /sys/kernel/tracing/
  # echo osnoise &amp;gt; current_tracer
  # echo 0 &amp;gt; tracing_on
  # echo nop &amp;gt; current_tracer&lt;/p&gt;
&lt;p&gt;The osnoise tracer stops the workload when no trace instance
is actually collecting data. This can be caused both by
disabling tracing or disabling the tracer itself.&lt;/p&gt;
&lt;p&gt;To avoid unregistering events…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48848</guid>
    </item>
    <item>
      <title>GHSA-6gcc-c84m-wqv4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6gcc-c84m-wqv4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/osnoise: Do not unregister events twice&lt;/p&gt;
&lt;p&gt;Nicolas reported that using:&lt;/p&gt;
&lt;p&gt;# trace-cmd record -e all -M 10 -p osnoise --poll&lt;/p&gt;
&lt;p&gt;Resulted in the following kernel warning:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370
 [...]
 CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19
 RIP: 0010:tracepoint_probe_unregister+0x280/0x370
 [...]
 CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0
 Call Trace:
  &amp;lt;TASK&amp;gt;
  osnoise_workload_stop+0x36/0x90
  tracing_set_tracer+0x108/0x260
  tracing_set_trace_write+0x94/0xd0
  ? __check_object_size.part.0+0x10a/0x150
  ? selinux_file_permission+0x104/0x150
  vfs_write+0xb5/0x290
  ksys_write+0x5f/0xe0
  do_syscall_64+0x3b/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae
 RIP: 0033:0x7ff919a18127
 [...]
 ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;The warning complains about an attempt to unregister an
unregistered tracepoint.&lt;/p&gt;
&lt;p&gt;This happens on trace-cmd because it first stops tracing, and
then switches the tracer to nop. Which is equivalent to:&lt;/p&gt;
&lt;p&gt;# cd /sys/kernel/tracing/
  # echo osnoise &amp;gt; current_tracer
  # echo 0 &amp;gt; tracing_on
  # echo nop &amp;gt; current_tracer&lt;/p&gt;
&lt;p&gt;The osnoise tracer stops the workload when no trace instance
is actually collecting data. This can be caused both by
disabling tracing or disabling the tracer itself.&lt;/p&gt;
&lt;p&gt;To avoid unregistering events…&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;tracing/osnoise: Do not unregister events twice&lt;/p&gt;
&lt;p&gt;Nicolas reported that using:&lt;/p&gt;
&lt;p&gt;# trace-cmd record -e all -M 10 -p osnoise --poll&lt;/p&gt;
&lt;p&gt;Resulted in the following kernel warning:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370
 [...]
 CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19
 RIP: 0010:tracepoint_probe_unregister+0x280/0x370
 [...]
 CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0
 Call Trace:
  &amp;lt;TASK&amp;gt;
  osnoise_workload_stop+0x36/0x90
  tracing_set_tracer+0x108/0x260
  tracing_set_trace_write+0x94/0xd0
  ? __check_object_size.part.0+0x10a/0x150
  ? selinux_file_permission+0x104/0x150
  vfs_write+0xb5/0x290
  ksys_write+0x5f/0xe0
  do_syscall_64+0x3b/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae
 RIP: 0033:0x7ff919a18127
 [...]
 ---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;The warning complains about an attempt to unregister an
unregistered tracepoint.&lt;/p&gt;
&lt;p&gt;This happens on trace-cmd because it first stops tracing, and
then switches the tracer to nop. Which is equivalent to:&lt;/p&gt;
&lt;p&gt;# cd /sys/kernel/tracing/
  # echo osnoise &amp;gt; current_tracer
  # echo 0 &amp;gt; tracing_on
  # echo nop &amp;gt; current_tracer&lt;/p&gt;
&lt;p&gt;The osnoise tracer stops the workload when no trace instance
is actually collecting data. This can be caused both by
disabling tracing or disabling the tracer itself.&lt;/p&gt;
&lt;p&gt;To avoid unregistering events…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6gcc-c84m-wqv4</guid>
    </item>
    <item>
      <title>OESA-2024-2257 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2257</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix kernel crash during module removal&#13;
&#13;
The driver incorrectly frees client instance and subsequent
i40e module removal leads to kernel crash.&#13;
&#13;
Reproducer:
1. Do ethtool offline test followed immediately by another one
host# ethtool -t eth0 offline; ethtool -t eth0 offline
2. Remove recursively irdma module that also removes i40e module
host# modprobe -r irdma&#13;
&#13;
Result:
[ 8675.035651] i40e 0000:3d:00.0 eno1: offline testing starting
[ 8675.193774] i40e 0000:3d:00.0 eno1: testing finished
[ 8675.201316] i40e 0000:3d:00.0 eno1: offline testing starting
[ 8675.358921] i40e 0000:3d:00.0 eno1: testing finished
[ 8675.496921] i40e 0000:3d:00.0: IRDMA hardware initialization FAILED init_state=2 status=-110
[ 8686.188955] i40e 0000:3d:00.1: i40e_ptp_stop: removed PHC on eno2
[ 8686.943890] i40e 0000:3d:00.1: Deleted LAN device PF1 bus=0x3d dev=0x00 func=0x01
[ 8686.952669] i40e 0000:3d:00.0: i40e_ptp_stop: removed PHC on eno1
[ 8687.761787] BUG: kernel NULL pointer dereference, address: 0000000000000030
[ 8687.768755] #PF: supervisor read access in kernel mode
[ 8687.773895] #PF: error_code(0x0000) - not-present page
[ 8687.779034] PGD 0 P4D 0
[ 8687.781575] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 8687.785935] CPU: 51 PID: 172891 Comm: rmmod Kdump: loaded Tainted: G        W I        5.19.0+ #2
[ 8687.794800] Hardware name: Intel C…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix kernel crash during module removal&#13;
&#13;
The driver incorrectly frees client instance and subsequent
i40e module removal leads to kernel crash.&#13;
&#13;
Reproducer:
1. Do ethtool offline test followed immediately by another one
host# ethtool -t eth0 offline; ethtool -t eth0 offline
2. Remove recursively irdma module that also removes i40e module
host# modprobe -r irdma&#13;
&#13;
Result:
[ 8675.035651] i40e 0000:3d:00.0 eno1: offline testing starting
[ 8675.193774] i40e 0000:3d:00.0 eno1: testing finished
[ 8675.201316] i40e 0000:3d:00.0 eno1: offline testing starting
[ 8675.358921] i40e 0000:3d:00.0 eno1: testing finished
[ 8675.496921] i40e 0000:3d:00.0: IRDMA hardware initialization FAILED init_state=2 status=-110
[ 8686.188955] i40e 0000:3d:00.1: i40e_ptp_stop: removed PHC on eno2
[ 8686.943890] i40e 0000:3d:00.1: Deleted LAN device PF1 bus=0x3d dev=0x00 func=0x01
[ 8686.952669] i40e 0000:3d:00.0: i40e_ptp_stop: removed PHC on eno1
[ 8687.761787] BUG: kernel NULL pointer dereference, address: 0000000000000030
[ 8687.768755] #PF: supervisor read access in kernel mode
[ 8687.773895] #PF: error_code(0x0000) - not-present page
[ 8687.779034] PGD 0 P4D 0
[ 8687.781575] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 8687.785935] CPU: 51 PID: 172891 Comm: rmmod Kdump: loaded Tainted: G        W I        5.19.0+ #2
[ 8687.794800] Hardware name: Intel C…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2257</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48848</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48848</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 57 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Do not unregister events twice Nicolas reported that using:  # trace-cmd record -e all -M 10 -p osnoise --poll Resulted in the following kernel warning:  ------------[ cut here ]------------  WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370  [...]  CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19  RIP: 0010:tracepoint_probe_unregister+0x280/0x370  [...]  CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0  Call Trace:   &amp;lt;TASK&amp;gt;   osnoise_workload_stop+0x36/0x90   tracing_set_tracer+0x108/0x260   tracing_set_trace_write+0x94/0xd0   ? __check_object_size.part.0+0x10a/0x150   ? selinux_file_permission+0x104/0x150   vfs_write+0xb5/0x290   ksys_write+0x5f/0xe0   do_syscall_64+0x3b/0x90   entry_SYSCALL_64_after_hwframe+0x44/0xae  RIP: 0033:0x7ff919a18127  [...]  ---[ end trace 0000000000000000 ]--- The warning complains about an attempt to unregister an unregistered tracepoint. This happens on trace-cmd because it first stops tracing, and then switches the tracer to nop. Which is equivalent to:   # cd /sys/kernel/tracing/   # echo osnoise &amp;gt; current_tracer   # echo 0 &amp;gt; tracing_on   # echo nop &amp;gt; current_tracer The osnoise tracer stops the workload when no trace instance is actually collecting data. This can be caused both by disabling tracing or disabling the tracer itself. To avoid unregistering events twice, us…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 57 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Do not unregister events twice Nicolas reported that using:  # trace-cmd record -e all -M 10 -p osnoise --poll Resulted in the following kernel warning:  ------------[ cut here ]------------  WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370  [...]  CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19  RIP: 0010:tracepoint_probe_unregister+0x280/0x370  [...]  CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0  Call Trace:   &amp;lt;TASK&amp;gt;   osnoise_workload_stop+0x36/0x90   tracing_set_tracer+0x108/0x260   tracing_set_trace_write+0x94/0xd0   ? __check_object_size.part.0+0x10a/0x150   ? selinux_file_permission+0x104/0x150   vfs_write+0xb5/0x290   ksys_write+0x5f/0xe0   do_syscall_64+0x3b/0x90   entry_SYSCALL_64_after_hwframe+0x44/0xae  RIP: 0033:0x7ff919a18127  [...]  ---[ end trace 0000000000000000 ]--- The warning complains about an attempt to unregister an unregistered tracepoint. This happens on trace-cmd because it first stops tracing, and then switches the tracer to nop. Which is equivalent to:   # cd /sys/kernel/tracing/   # echo osnoise &amp;gt; current_tracer   # echo 0 &amp;gt; tracing_on   # echo nop &amp;gt; current_tracer The osnoise tracer stops the workload when no trace instance is actually collecting data. This can be caused both by disabling tracing or disabling the tracer itself. To avoid unregistering events twice, us…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48848</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1625 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</guid>
    </item>
  </channel>
</rss>
