<?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 23:39:52 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03980</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03980</link>
      <description>bdu:2026-03980</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03980</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53031</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53031</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53031</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0336 — 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-0336</link>
      <description>certfr-2025-avi-0336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0336</guid>
    </item>
    <item>
      <title>EUVD-2026-311798</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311798</link>
      <description>EUVD-2026-311798</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311798</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53031</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53031</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/imc-pmu: Fix use of mutex in IRQs disabled section&lt;/p&gt;
&lt;p&gt;Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP
and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event.&lt;/p&gt;
&lt;p&gt;Command to trigger the warning:
  # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5&lt;/p&gt;
&lt;p&gt;Performance counter stats for &amp;#39;sleep 5&amp;#39;:&lt;/p&gt;
&lt;p&gt;0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/&lt;/p&gt;
&lt;p&gt;5.002117947 seconds time elapsed&lt;/p&gt;
&lt;p&gt;0.000131000 seconds user
         0.001063000 seconds sys&lt;/p&gt;
&lt;p&gt;Below is snippet of the warning in dmesg:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec
  preempt_count: 2, expected: 0
  4 locks held by perf-exec/2869:
   #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90
   #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0
   #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510
   #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510
  irq event stamp: 4806
  hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0
  hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510
  softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0
  softir…&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;powerpc/imc-pmu: Fix use of mutex in IRQs disabled section&lt;/p&gt;
&lt;p&gt;Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP
and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event.&lt;/p&gt;
&lt;p&gt;Command to trigger the warning:
  # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5&lt;/p&gt;
&lt;p&gt;Performance counter stats for &amp;#39;sleep 5&amp;#39;:&lt;/p&gt;
&lt;p&gt;0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/&lt;/p&gt;
&lt;p&gt;5.002117947 seconds time elapsed&lt;/p&gt;
&lt;p&gt;0.000131000 seconds user
         0.001063000 seconds sys&lt;/p&gt;
&lt;p&gt;Below is snippet of the warning in dmesg:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec
  preempt_count: 2, expected: 0
  4 locks held by perf-exec/2869:
   #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90
   #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0
   #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510
   #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510
  irq event stamp: 4806
  hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0
  hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510
  softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0
  softir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53031</guid>
    </item>
    <item>
      <title>GHSA-jph2-wv5j-5w33</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jph2-wv5j-5w33</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/imc-pmu: Fix use of mutex in IRQs disabled section&lt;/p&gt;
&lt;p&gt;Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP
and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event.&lt;/p&gt;
&lt;p&gt;Command to trigger the warning:
  # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5&lt;/p&gt;
&lt;p&gt;Performance counter stats for &amp;#39;sleep 5&amp;#39;:&lt;/p&gt;
&lt;p&gt;0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/&lt;/p&gt;
&lt;p&gt;5.002117947 seconds time elapsed&lt;/p&gt;
&lt;p&gt;0.000131000 seconds user
         0.001063000 seconds sys&lt;/p&gt;
&lt;p&gt;Below is snippet of the warning in dmesg:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec
  preempt_count: 2, expected: 0
  4 locks held by perf-exec/2869:
   #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90
   #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0
   #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510
   #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510
  irq event stamp: 4806
  hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0
  hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510
  softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0
  softir…&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;powerpc/imc-pmu: Fix use of mutex in IRQs disabled section&lt;/p&gt;
&lt;p&gt;Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP
and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event.&lt;/p&gt;
&lt;p&gt;Command to trigger the warning:
  # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5&lt;/p&gt;
&lt;p&gt;Performance counter stats for &amp;#39;sleep 5&amp;#39;:&lt;/p&gt;
&lt;p&gt;0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/&lt;/p&gt;
&lt;p&gt;5.002117947 seconds time elapsed&lt;/p&gt;
&lt;p&gt;0.000131000 seconds user
         0.001063000 seconds sys&lt;/p&gt;
&lt;p&gt;Below is snippet of the warning in dmesg:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec
  preempt_count: 2, expected: 0
  4 locks held by perf-exec/2869:
   #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90
   #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0
   #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510
   #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510
  irq event stamp: 4806
  hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0
  hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510
  softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0
  softir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jph2-wv5j-5w33</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — security update for kernel</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01620-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01620-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:01620-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53031</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53031</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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4 and 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/imc-pmu: Fix use of mutex in IRQs disabled section Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event. Command to trigger the warning:   # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5    Performance counter stats for &amp;#39;sleep 5&amp;#39;:                    0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/          5.002117947 seconds time elapsed          0.000131000 seconds user          0.001063000 seconds sys Below is snippet of the warning in dmesg:   BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580   in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec   preempt_count: 2, expected: 0   4 locks held by perf-exec/2869:    #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90    #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0    #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510    #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510   irq event stamp: 4806   hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0   hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510   softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0   softirqs last d…&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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4 and 141 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/imc-pmu: Fix use of mutex in IRQs disabled section Current imc-pmu code triggers a WARNING with CONFIG_DEBUG_ATOMIC_SLEEP and CONFIG_PROVE_LOCKING enabled, while running a thread_imc event. Command to trigger the warning:   # perf stat -e thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/ sleep 5    Performance counter stats for &amp;#39;sleep 5&amp;#39;:                    0      thread_imc/CPM_CS_FROM_L4_MEM_X_DPTEG/          5.002117947 seconds time elapsed          0.000131000 seconds user          0.001063000 seconds sys Below is snippet of the warning in dmesg:   BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580   in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 2869, name: perf-exec   preempt_count: 2, expected: 0   4 locks held by perf-exec/2869:    #0: c00000004325c540 (&amp;amp;sig-&amp;gt;cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x64/0xa90    #1: c00000004325c5d8 (&amp;amp;sig-&amp;gt;exec_update_lock){++++}-{3:3}, at: begin_new_exec+0x460/0xef0    #2: c0000003fa99d4e0 (&amp;amp;cpuctx_lock){-...}-{2:2}, at: perf_event_exec+0x290/0x510    #3: c000000017ab8418 (&amp;amp;ctx-&amp;gt;lock){....}-{2:2}, at: perf_event_exec+0x29c/0x510   irq event stamp: 4806   hardirqs last  enabled at (4805): [&amp;lt;c000000000f65b94&amp;gt;] _raw_spin_unlock_irqrestore+0x94/0xd0   hardirqs last disabled at (4806): [&amp;lt;c0000000003fae44&amp;gt;] perf_event_exec+0x394/0x510   softirqs last  enabled at (0): [&amp;lt;c00000000013c404&amp;gt;] copy_process+0xc34/0x1ff0   softirqs last d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53031</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0649 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</guid>
    </item>
  </channel>
</rss>
