<?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>Tue, 06 Oct 2026 21:37:36 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04498</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04498</link>
      <description>bdu:2026-04498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04498</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0607 — 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-0607</link>
      <description>certfr-2025-avi-0607</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0607</guid>
    </item>
    <item>
      <title>EUVD-2026-310789</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310789</link>
      <description>EUVD-2026-310789</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310789</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49764</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49764</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Prevent bpf program recursion for raw tracepoint probes&lt;/p&gt;
&lt;p&gt;We got report from sysbot [1] about warnings that were caused by
bpf program attached to contention_begin raw tracepoint triggering
the same tracepoint by using bpf_trace_printk helper that takes
trace_printk_lock lock.&lt;/p&gt;
&lt;p&gt;Call Trace:
  &amp;lt;TASK&amp;gt;
  ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90
  bpf_trace_printk+0x2b/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  __unfreeze_partials+0x5b/0x160
  ...&lt;/p&gt;
&lt;p&gt;The can be reproduced by attaching bpf program as raw tracepoint on
contention_begin tracepoint. The bpf prog calls bpf_trace_printk
helper. Then by running perf bench the spin lock code is forced to
take slow path and call contention_begin tracepoint.&lt;/p&gt;
&lt;p&gt;Fixing this by skipping execution of the bpf program i…&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;bpf: Prevent bpf program recursion for raw tracepoint probes&lt;/p&gt;
&lt;p&gt;We got report from sysbot [1] about warnings that were caused by
bpf program attached to contention_begin raw tracepoint triggering
the same tracepoint by using bpf_trace_printk helper that takes
trace_printk_lock lock.&lt;/p&gt;
&lt;p&gt;Call Trace:
  &amp;lt;TASK&amp;gt;
  ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90
  bpf_trace_printk+0x2b/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  __unfreeze_partials+0x5b/0x160
  ...&lt;/p&gt;
&lt;p&gt;The can be reproduced by attaching bpf program as raw tracepoint on
contention_begin tracepoint. The bpf prog calls bpf_trace_printk
helper. Then by running perf bench the spin lock code is forced to
take slow path and call contention_begin tracepoint.&lt;/p&gt;
&lt;p&gt;Fixing this by skipping execution of the bpf program i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49764</guid>
    </item>
    <item>
      <title>GHSA-7wj3-cv8c-chpx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7wj3-cv8c-chpx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Prevent bpf program recursion for raw tracepoint probes&lt;/p&gt;
&lt;p&gt;We got report from sysbot [1] about warnings that were caused by
bpf program attached to contention_begin raw tracepoint triggering
the same tracepoint by using bpf_trace_printk helper that takes
trace_printk_lock lock.&lt;/p&gt;
&lt;p&gt;Call Trace:
  &amp;lt;TASK&amp;gt;
  ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90
  bpf_trace_printk+0x2b/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  __unfreeze_partials+0x5b/0x160
  ...&lt;/p&gt;
&lt;p&gt;The can be reproduced by attaching bpf program as raw tracepoint on
contention_begin tracepoint. The bpf prog calls bpf_trace_printk
helper. Then by running perf bench the spin lock code is forced to
take slow path and call contention_begin tracepoint.&lt;/p&gt;
&lt;p&gt;Fixing this by skipping execution of the bpf program i…&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;bpf: Prevent bpf program recursion for raw tracepoint probes&lt;/p&gt;
&lt;p&gt;We got report from sysbot [1] about warnings that were caused by
bpf program attached to contention_begin raw tracepoint triggering
the same tracepoint by using bpf_trace_printk helper that takes
trace_printk_lock lock.&lt;/p&gt;
&lt;p&gt;Call Trace:
  &amp;lt;TASK&amp;gt;
  ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90
  bpf_trace_printk+0x2b/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  bpf_trace_printk+0x3f/0xe0
  bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
  bpf_trace_run2+0x26/0x90
  native_queued_spin_lock_slowpath+0x1c6/0x2b0
  _raw_spin_lock_irqsave+0x44/0x50
  __unfreeze_partials+0x5b/0x160
  ...&lt;/p&gt;
&lt;p&gt;The can be reproduced by attaching bpf program as raw tracepoint on
contention_begin tracepoint. The bpf prog calls bpf_trace_printk
helper. Then by running perf bench the spin lock code is forced to
take slow path and call contention_begin tracepoint.&lt;/p&gt;
&lt;p&gt;Fixing this by skipping execution of the bpf program i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7wj3-cv8c-chpx</guid>
    </item>
    <item>
      <title>msrc_CVE-2022-49764 — bpf: Prevent bpf program recursion for raw tracepoint probes</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2022-49764</link>
      <description>msrc_CVE-2022-49764</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2022-49764</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02334-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02334-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:02334-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49764</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49764</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent bpf program recursion for raw tracepoint probes We got report from sysbot [1] about warnings that were caused by bpf program attached to contention_begin raw tracepoint triggering the same tracepoint by using bpf_trace_printk helper that takes trace_printk_lock lock.  Call Trace:   &amp;lt;TASK&amp;gt;   ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90   bpf_trace_printk+0x2b/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   __unfreeze_partials+0x5b/0x160   ... The can be reproduced by attaching bpf program as raw tracepoint on contention_begin tracepoint. The bpf prog calls bpf_trace_printk helper. Then by running perf bench the spin lock code is forced to take slow path and call contention_begin tracepoint. Fixing this by skipping execution of the bpf program if it&amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent bpf program recursion for raw tracepoint probes We got report from sysbot [1] about warnings that were caused by bpf program attached to contention_begin raw tracepoint triggering the same tracepoint by using bpf_trace_printk helper that takes trace_printk_lock lock.  Call Trace:   &amp;lt;TASK&amp;gt;   ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90   bpf_trace_printk+0x2b/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   bpf_trace_printk+0x3f/0xe0   bpf_prog_a9aec6167c091eef_prog+0x1f/0x24   bpf_trace_run2+0x26/0x90   native_queued_spin_lock_slowpath+0x1c6/0x2b0   _raw_spin_lock_irqsave+0x44/0x50   __unfreeze_partials+0x5b/0x160   ... The can be reproduced by attaching bpf program as raw tracepoint on contention_begin tracepoint. The bpf prog calls bpf_trace_printk helper. Then by running perf bench the spin lock code is forced to take slow path and call contention_begin tracepoint. Fixing this by skipping execution of the bpf program if it&amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49764</guid>
    </item>
  </channel>
</rss>
