<?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 08:06:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10374</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10374</link>
      <description>bdu:2026-10374</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10374</guid>
    </item>
    <item>
      <title>EUVD-2026-311359</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311359</link>
      <description>EUVD-2026-311359</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311359</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50648</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50648</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller&lt;/p&gt;
&lt;p&gt;Naveen reported recursive locking of direct_mutex with sample
ftrace-direct-modify.ko:&lt;/p&gt;
&lt;p&gt;[   74.762406] WARNING: possible recursive locking detected
[   74.762887] 6.0.0-rc6+ #33 Not tainted
[   74.763216] --------------------------------------------
[   74.763672] event-sample-fn/1084 is trying to acquire lock:
[   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    register_ftrace_function+0x1f/0x180
[   74.764922]
[   74.764922] but task is already holding lock:
[   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.766142]
[   74.766142] other info that might help us debug this:
[   74.766701]  Possible unsafe locking scenario:
[   74.766701]
[   74.767216]        CPU0
[   74.767437]        ----
[   74.767656]   lock(direct_mutex);
[   74.767952]   lock(direct_mutex);
[   74.768245]
[   74.768245]  *** DEADLOCK ***
[   74.768245]
[   74.768750]  May be due to missing lock nesting notation
[   74.768750]
[   74.769332] 1 lock held by event-sample-fn/1084:
[   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.770496]
[   74.770496] stack backtrace:
[   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ...
[   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...
[   74.772474] Ca…&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;ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller&lt;/p&gt;
&lt;p&gt;Naveen reported recursive locking of direct_mutex with sample
ftrace-direct-modify.ko:&lt;/p&gt;
&lt;p&gt;[   74.762406] WARNING: possible recursive locking detected
[   74.762887] 6.0.0-rc6+ #33 Not tainted
[   74.763216] --------------------------------------------
[   74.763672] event-sample-fn/1084 is trying to acquire lock:
[   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    register_ftrace_function+0x1f/0x180
[   74.764922]
[   74.764922] but task is already holding lock:
[   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.766142]
[   74.766142] other info that might help us debug this:
[   74.766701]  Possible unsafe locking scenario:
[   74.766701]
[   74.767216]        CPU0
[   74.767437]        ----
[   74.767656]   lock(direct_mutex);
[   74.767952]   lock(direct_mutex);
[   74.768245]
[   74.768245]  *** DEADLOCK ***
[   74.768245]
[   74.768750]  May be due to missing lock nesting notation
[   74.768750]
[   74.769332] 1 lock held by event-sample-fn/1084:
[   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.770496]
[   74.770496] stack backtrace:
[   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ...
[   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...
[   74.772474] Ca…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50648</guid>
    </item>
    <item>
      <title>GHSA-qjqh-pmxv-4qmf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qjqh-pmxv-4qmf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller&lt;/p&gt;
&lt;p&gt;Naveen reported recursive locking of direct_mutex with sample
ftrace-direct-modify.ko:&lt;/p&gt;
&lt;p&gt;[   74.762406] WARNING: possible recursive locking detected
[   74.762887] 6.0.0-rc6+ #33 Not tainted
[   74.763216] --------------------------------------------
[   74.763672] event-sample-fn/1084 is trying to acquire lock:
[   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    register_ftrace_function+0x1f/0x180
[   74.764922]
[   74.764922] but task is already holding lock:
[   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.766142]
[   74.766142] other info that might help us debug this:
[   74.766701]  Possible unsafe locking scenario:
[   74.766701]
[   74.767216]        CPU0
[   74.767437]        ----
[   74.767656]   lock(direct_mutex);
[   74.767952]   lock(direct_mutex);
[   74.768245]
[   74.768245]  *** DEADLOCK ***
[   74.768245]
[   74.768750]  May be due to missing lock nesting notation
[   74.768750]
[   74.769332] 1 lock held by event-sample-fn/1084:
[   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.770496]
[   74.770496] stack backtrace:
[   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ...
[   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...
[   74.772474] Ca…&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;ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller&lt;/p&gt;
&lt;p&gt;Naveen reported recursive locking of direct_mutex with sample
ftrace-direct-modify.ko:&lt;/p&gt;
&lt;p&gt;[   74.762406] WARNING: possible recursive locking detected
[   74.762887] 6.0.0-rc6+ #33 Not tainted
[   74.763216] --------------------------------------------
[   74.763672] event-sample-fn/1084 is trying to acquire lock:
[   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    register_ftrace_function+0x1f/0x180
[   74.764922]
[   74.764922] but task is already holding lock:
[   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.766142]
[   74.766142] other info that might help us debug this:
[   74.766701]  Possible unsafe locking scenario:
[   74.766701]
[   74.767216]        CPU0
[   74.767437]        ----
[   74.767656]   lock(direct_mutex);
[   74.767952]   lock(direct_mutex);
[   74.768245]
[   74.768245]  *** DEADLOCK ***
[   74.768245]
[   74.768750]  May be due to missing lock nesting notation
[   74.768750]
[   74.769332] 1 lock held by event-sample-fn/1084:
[   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \
    modify_ftrace_direct+0x34/0x1f0
[   74.770496]
[   74.770496] stack backtrace:
[   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ...
[   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...
[   74.772474] Ca…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qjqh-pmxv-4qmf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50648</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50648</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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller Naveen reported recursive locking of direct_mutex with sample ftrace-direct-modify.ko: [   74.762406] WARNING: possible recursive locking detected [   74.762887] 6.0.0-rc6+ #33 Not tainted [   74.763216] -------------------------------------------- [   74.763672] event-sample-fn/1084 is trying to acquire lock: [   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     register_ftrace_function+0x1f/0x180 [   74.764922] [   74.764922] but task is already holding lock: [   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     modify_ftrace_direct+0x34/0x1f0 [   74.766142] [   74.766142] other info that might help us debug this: [   74.766701]  Possible unsafe locking scenario: [   74.766701] [   74.767216]        CPU0 [   74.767437]        ---- [   74.767656]   lock(direct_mutex); [   74.767952]   lock(direct_mutex); [   74.768245] [   74.768245]  *** DEADLOCK *** [   74.768245] [   74.768750]  May be due to missing lock nesting notation [   74.768750] [   74.769332] 1 lock held by event-sample-fn/1084: [   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     modify_ftrace_direct+0x34/0x1f0 [   74.770496] [   74.770496] stack backtrace: [   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ... [   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ... [   74.772474] Call…&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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller Naveen reported recursive locking of direct_mutex with sample ftrace-direct-modify.ko: [   74.762406] WARNING: possible recursive locking detected [   74.762887] 6.0.0-rc6+ #33 Not tainted [   74.763216] -------------------------------------------- [   74.763672] event-sample-fn/1084 is trying to acquire lock: [   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     register_ftrace_function+0x1f/0x180 [   74.764922] [   74.764922] but task is already holding lock: [   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     modify_ftrace_direct+0x34/0x1f0 [   74.766142] [   74.766142] other info that might help us debug this: [   74.766701]  Possible unsafe locking scenario: [   74.766701] [   74.767216]        CPU0 [   74.767437]        ---- [   74.767656]   lock(direct_mutex); [   74.767952]   lock(direct_mutex); [   74.768245] [   74.768245]  *** DEADLOCK *** [   74.768245] [   74.768750]  May be due to missing lock nesting notation [   74.768750] [   74.769332] 1 lock held by event-sample-fn/1084: [   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \     modify_ftrace_direct+0x34/0x1f0 [   74.770496] [   74.770496] stack backtrace: [   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ... [   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ... [   74.772474] Call…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50648</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765</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-2765</guid>
    </item>
  </channel>
</rss>
