<?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 05:25:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01934</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01934</link>
      <description>bdu:2025-01934</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01934</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-43870</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-43870</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-43870</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0870 — 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-2024-avi-0870</link>
      <description>certfr-2024-avi-0870</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0870</guid>
    </item>
    <item>
      <title>EUVD-2026-320681</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320681</link>
      <description>EUVD-2026-320681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320681</guid>
    </item>
    <item>
      <title>fkie_cve-2024-43870</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43870</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix event leak upon exit&lt;/p&gt;
&lt;p&gt;When a task is scheduled out, pending sigtrap deliveries are deferred
to the target task upon resume to userspace via task_work.&lt;/p&gt;
&lt;p&gt;However failures while adding an event&amp;#39;s callback to the task_work
engine are ignored. And since the last call for events exit happen
after task work is eventually closed, there is a small window during
which pending sigtrap can be queued though ignored, leaking the event
refcount addition such as in the following scenario:&lt;/p&gt;
&lt;p&gt;TASK A
    -----&lt;/p&gt;
&lt;p&gt;do_exit()
       exit_task_work(tsk);&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
       perf_event_overflow()
          event-&amp;gt;pending_sigtrap = pending_id;
          irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);
       &amp;lt;/IRQ&amp;gt;
    =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B
       event_sched_out()
          event-&amp;gt;pending_sigtrap = 0;
          atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)
          // FAILS: task work has exited
          task_work_add(&amp;amp;event-&amp;gt;pending_task)
       [...]
       &amp;lt;IRQ WORK&amp;gt;
       perf_pending_irq()
          // early return: event-&amp;gt;oncpu = -1
       &amp;lt;/IRQ WORK&amp;gt;
       [...]
    =========&amp;gt; TASK B -&amp;gt; TASK A
       perf_event_exit_task(tsk)
          perf_event_exit_event()
             free_event()
                WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)
                // leak event due to unexpected refcount == 2&lt;/p&gt;
&lt;p&gt;As a result the event is never released while the task exits.&lt;/p&gt;
&lt;p&gt;Fix this with appropria…&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;perf: Fix event leak upon exit&lt;/p&gt;
&lt;p&gt;When a task is scheduled out, pending sigtrap deliveries are deferred
to the target task upon resume to userspace via task_work.&lt;/p&gt;
&lt;p&gt;However failures while adding an event&amp;#39;s callback to the task_work
engine are ignored. And since the last call for events exit happen
after task work is eventually closed, there is a small window during
which pending sigtrap can be queued though ignored, leaking the event
refcount addition such as in the following scenario:&lt;/p&gt;
&lt;p&gt;TASK A
    -----&lt;/p&gt;
&lt;p&gt;do_exit()
       exit_task_work(tsk);&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
       perf_event_overflow()
          event-&amp;gt;pending_sigtrap = pending_id;
          irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);
       &amp;lt;/IRQ&amp;gt;
    =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B
       event_sched_out()
          event-&amp;gt;pending_sigtrap = 0;
          atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)
          // FAILS: task work has exited
          task_work_add(&amp;amp;event-&amp;gt;pending_task)
       [...]
       &amp;lt;IRQ WORK&amp;gt;
       perf_pending_irq()
          // early return: event-&amp;gt;oncpu = -1
       &amp;lt;/IRQ WORK&amp;gt;
       [...]
    =========&amp;gt; TASK B -&amp;gt; TASK A
       perf_event_exit_task(tsk)
          perf_event_exit_event()
             free_event()
                WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)
                // leak event due to unexpected refcount == 2&lt;/p&gt;
&lt;p&gt;As a result the event is never released while the task exits.&lt;/p&gt;
&lt;p&gt;Fix this with appropria…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-43870</guid>
    </item>
    <item>
      <title>GHSA-24f8-f4wm-56gg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-24f8-f4wm-56gg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix event leak upon exit&lt;/p&gt;
&lt;p&gt;When a task is scheduled out, pending sigtrap deliveries are deferred
to the target task upon resume to userspace via task_work.&lt;/p&gt;
&lt;p&gt;However failures while adding an event&amp;#39;s callback to the task_work
engine are ignored. And since the last call for events exit happen
after task work is eventually closed, there is a small window during
which pending sigtrap can be queued though ignored, leaking the event
refcount addition such as in the following scenario:&lt;/p&gt;
&lt;p&gt;TASK A
    -----&lt;/p&gt;
&lt;p&gt;do_exit()
       exit_task_work(tsk);&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
       perf_event_overflow()
          event-&amp;gt;pending_sigtrap = pending_id;
          irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);
       &amp;lt;/IRQ&amp;gt;
    =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B
       event_sched_out()
          event-&amp;gt;pending_sigtrap = 0;
          atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)
          // FAILS: task work has exited
          task_work_add(&amp;amp;event-&amp;gt;pending_task)
       [...]
       &amp;lt;IRQ WORK&amp;gt;
       perf_pending_irq()
          // early return: event-&amp;gt;oncpu = -1
       &amp;lt;/IRQ WORK&amp;gt;
       [...]
    =========&amp;gt; TASK B -&amp;gt; TASK A
       perf_event_exit_task(tsk)
          perf_event_exit_event()
             free_event()
                WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)
                // leak event due to unexpected refcount == 2&lt;/p&gt;
&lt;p&gt;As a result the event is never released while the task exits.&lt;/p&gt;
&lt;p&gt;Fix this with appropria…&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;perf: Fix event leak upon exit&lt;/p&gt;
&lt;p&gt;When a task is scheduled out, pending sigtrap deliveries are deferred
to the target task upon resume to userspace via task_work.&lt;/p&gt;
&lt;p&gt;However failures while adding an event&amp;#39;s callback to the task_work
engine are ignored. And since the last call for events exit happen
after task work is eventually closed, there is a small window during
which pending sigtrap can be queued though ignored, leaking the event
refcount addition such as in the following scenario:&lt;/p&gt;
&lt;p&gt;TASK A
    -----&lt;/p&gt;
&lt;p&gt;do_exit()
       exit_task_work(tsk);&lt;/p&gt;
&lt;p&gt;&amp;lt;IRQ&amp;gt;
       perf_event_overflow()
          event-&amp;gt;pending_sigtrap = pending_id;
          irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);
       &amp;lt;/IRQ&amp;gt;
    =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B
       event_sched_out()
          event-&amp;gt;pending_sigtrap = 0;
          atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)
          // FAILS: task work has exited
          task_work_add(&amp;amp;event-&amp;gt;pending_task)
       [...]
       &amp;lt;IRQ WORK&amp;gt;
       perf_pending_irq()
          // early return: event-&amp;gt;oncpu = -1
       &amp;lt;/IRQ WORK&amp;gt;
       [...]
    =========&amp;gt; TASK B -&amp;gt; TASK A
       perf_event_exit_task(tsk)
          perf_event_exit_event()
             free_event()
                WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)
                // leak event due to unexpected refcount == 2&lt;/p&gt;
&lt;p&gt;As a result the event is never released while the task exits.&lt;/p&gt;
&lt;p&gt;Fix this with appropria…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-24f8-f4wm-56gg</guid>
    </item>
    <item>
      <title>OESA-2025-1097 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1097</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1097</guid>
    </item>
    <item>
      <title>RHSA-2024:9315 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:9315</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:9315</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3551-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3551-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-2024:3551-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-43870</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43870</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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exit When a task is scheduled out, pending sigtrap deliveries are deferred to the target task upon resume to userspace via task_work. However failures while adding an event&amp;#39;s callback to the task_work engine are ignored. And since the last call for events exit happen after task work is eventually closed, there is a small window during which pending sigtrap can be queued though ignored, leaking the event refcount addition such as in the following scenario:     TASK A     -----     do_exit()        exit_task_work(tsk);        &amp;lt;IRQ&amp;gt;        perf_event_overflow()           event-&amp;gt;pending_sigtrap = pending_id;           irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);        &amp;lt;/IRQ&amp;gt;     =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B        event_sched_out()           event-&amp;gt;pending_sigtrap = 0;           atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)           // FAILS: task work has exited           task_work_add(&amp;amp;event-&amp;gt;pending_task)        [...]        &amp;lt;IRQ WORK&amp;gt;        perf_pending_irq()           // early return: event-&amp;gt;oncpu = -1        &amp;lt;/IRQ WORK&amp;gt;        [...]     =========&amp;gt; TASK B -&amp;gt; TASK A        perf_event_exit_task(tsk)           perf_event_exit_event()              free_event()                 WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)                 // leak event due to unexpected refcount == 2 As a result the event is never released while the task exits. Fix this with appropriate task_…&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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exit When a task is scheduled out, pending sigtrap deliveries are deferred to the target task upon resume to userspace via task_work. However failures while adding an event&amp;#39;s callback to the task_work engine are ignored. And since the last call for events exit happen after task work is eventually closed, there is a small window during which pending sigtrap can be queued though ignored, leaking the event refcount addition such as in the following scenario:     TASK A     -----     do_exit()        exit_task_work(tsk);        &amp;lt;IRQ&amp;gt;        perf_event_overflow()           event-&amp;gt;pending_sigtrap = pending_id;           irq_work_queue(&amp;amp;event-&amp;gt;pending_irq);        &amp;lt;/IRQ&amp;gt;     =========&amp;gt; PREEMPTION: TASK A -&amp;gt; TASK B        event_sched_out()           event-&amp;gt;pending_sigtrap = 0;           atomic_long_inc_not_zero(&amp;amp;event-&amp;gt;refcount)           // FAILS: task work has exited           task_work_add(&amp;amp;event-&amp;gt;pending_task)        [...]        &amp;lt;IRQ WORK&amp;gt;        perf_pending_irq()           // early return: event-&amp;gt;oncpu = -1        &amp;lt;/IRQ WORK&amp;gt;        [...]     =========&amp;gt; TASK B -&amp;gt; TASK A        perf_event_exit_task(tsk)           perf_event_exit_event()              free_event()                 WARN(atomic_long_cmpxchg(&amp;amp;event-&amp;gt;refcount, 1, 0) != 1)                 // leak event due to unexpected refcount == 2 As a result the event is never released while the task exits. Fix this with appropriate task_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43870</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1888 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1888</guid>
    </item>
  </channel>
</rss>
