<?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 11:24:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04667</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04667</link>
      <description>bdu:2025-04667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04667</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-54683</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-54683</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-54683</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0254 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254</link>
      <description>certfr-2025-avi-0254</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0254</guid>
    </item>
    <item>
      <title>EUVD-2026-313696</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313696</link>
      <description>EUVD-2026-313696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313696</guid>
    </item>
    <item>
      <title>fkie_cve-2024-54683</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-54683</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: IDLETIMER: Fix for possible ABBA deadlock&lt;/p&gt;
&lt;p&gt;Deletion of the last rule referencing a given idletimer may happen at
the same time as a read of its file in sysfs:&lt;/p&gt;
&lt;p&gt;| ======================================================
| WARNING: possible circular locking dependency detected
| 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted
| ------------------------------------------------------
| iptables/3303 is trying to acquire lock:
| ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20
|
| but task is already holding lock:
| ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v]
|
| which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;A simple reproducer is:&lt;/p&gt;
&lt;p&gt;| #!/bin/bash
|
| while true; do
|         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
|         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
| done &amp;amp;
| while true; do
|         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null
| done&lt;/p&gt;
&lt;p&gt;Avoid this by freeing list_mutex right after deleting the element from
the list, then continuing with the teardown.&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;netfilter: IDLETIMER: Fix for possible ABBA deadlock&lt;/p&gt;
&lt;p&gt;Deletion of the last rule referencing a given idletimer may happen at
the same time as a read of its file in sysfs:&lt;/p&gt;
&lt;p&gt;| ======================================================
| WARNING: possible circular locking dependency detected
| 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted
| ------------------------------------------------------
| iptables/3303 is trying to acquire lock:
| ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20
|
| but task is already holding lock:
| ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v]
|
| which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;A simple reproducer is:&lt;/p&gt;
&lt;p&gt;| #!/bin/bash
|
| while true; do
|         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
|         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
| done &amp;amp;
| while true; do
|         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null
| done&lt;/p&gt;
&lt;p&gt;Avoid this by freeing list_mutex right after deleting the element from
the list, then continuing with the teardown.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-54683</guid>
    </item>
    <item>
      <title>GHSA-4qcv-j3wr-hw24</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4qcv-j3wr-hw24</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: IDLETIMER: Fix for possible ABBA deadlock&lt;/p&gt;
&lt;p&gt;Deletion of the last rule referencing a given idletimer may happen at
the same time as a read of its file in sysfs:&lt;/p&gt;
&lt;p&gt;| ======================================================
| WARNING: possible circular locking dependency detected
| 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted
| ------------------------------------------------------
| iptables/3303 is trying to acquire lock:
| ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20
|
| but task is already holding lock:
| ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v]
|
| which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;A simple reproducer is:&lt;/p&gt;
&lt;p&gt;| #!/bin/bash
|
| while true; do
|         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
|         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
| done &amp;amp;
| while true; do
|         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null
| done&lt;/p&gt;
&lt;p&gt;Avoid this by freeing list_mutex right after deleting the element from
the list, then continuing with the teardown.&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;netfilter: IDLETIMER: Fix for possible ABBA deadlock&lt;/p&gt;
&lt;p&gt;Deletion of the last rule referencing a given idletimer may happen at
the same time as a read of its file in sysfs:&lt;/p&gt;
&lt;p&gt;| ======================================================
| WARNING: possible circular locking dependency detected
| 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted
| ------------------------------------------------------
| iptables/3303 is trying to acquire lock:
| ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20
|
| but task is already holding lock:
| ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v]
|
| which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;A simple reproducer is:&lt;/p&gt;
&lt;p&gt;| #!/bin/bash
|
| while true; do
|         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
|         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34;
| done &amp;amp;
| while true; do
|         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null
| done&lt;/p&gt;
&lt;p&gt;Avoid this by freeing list_mutex right after deleting the element from
the list, then continuing with the teardown.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4qcv-j3wr-hw24</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-54683 — netfilter: IDLETIMER: Fix for possible ABBA deadlock</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-54683</link>
      <description>msrc_CVE-2024-54683</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-54683</guid>
    </item>
    <item>
      <title>OESA-2025-1159 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1159</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;net: wwan: t7xx: Fix FSM command timeout issue&lt;/p&gt;
&lt;p&gt;When driver processes the internal state change command, it use an
asynchronous thread to process the command operation. If the main
thread detects that the task has timed out, the asynchronous thread
will panic when executing the completion notification because the
main thread completion object has been released.&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: fffffffffffffff8
PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
RIP: 0010:complete_all+0x3e/0xa0
[...]
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 ? __die_body+0x68/0xb0
 ? page_fault_oops+0x379/0x3e0
 ? exc_page_fault+0x69/0xa0
 ? asm_exc_page_fault+0x22/0x30
 ? complete_all+0x3e/0xa0
 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)]
 ? __pfx_autoremove_wake_function+0x10/0x10
 kthread+0xd8/0x110
 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)]
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x38/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;
[...]
CR2: fffffffffffffff8
---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;Use the reference counter to ensure safe release as Sergey suggests:
https://lore.kernel.org/all/da90f64c-260a-4329-87bf-1f9ff20a5951@gmail.com/(CVE-2024-39282)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: mipi-i3c-hci: Mask ring interrupts bef…&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;net: wwan: t7xx: Fix FSM command timeout issue&lt;/p&gt;
&lt;p&gt;When driver processes the internal state change command, it use an
asynchronous thread to process the command operation. If the main
thread detects that the task has timed out, the asynchronous thread
will panic when executing the completion notification because the
main thread completion object has been released.&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: fffffffffffffff8
PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
RIP: 0010:complete_all+0x3e/0xa0
[...]
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 ? __die_body+0x68/0xb0
 ? page_fault_oops+0x379/0x3e0
 ? exc_page_fault+0x69/0xa0
 ? asm_exc_page_fault+0x22/0x30
 ? complete_all+0x3e/0xa0
 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)]
 ? __pfx_autoremove_wake_function+0x10/0x10
 kthread+0xd8/0x110
 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)]
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x38/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;
[...]
CR2: fffffffffffffff8
---[ end trace 0000000000000000 ]---&lt;/p&gt;
&lt;p&gt;Use the reference counter to ensure safe release as Sergey suggests:
https://lore.kernel.org/all/da90f64c-260a-4329-87bf-1f9ff20a5951@gmail.com/(CVE-2024-39282)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: mipi-i3c-hci: Mask ring interrupts bef…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1159</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01600-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:01600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-54683</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-54683</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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: IDLETIMER: Fix for possible ABBA deadlock Deletion of the last rule referencing a given idletimer may happen at the same time as a read of its file in sysfs: | ====================================================== | WARNING: possible circular locking dependency detected | 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted | ------------------------------------------------------ | iptables/3303 is trying to acquire lock: | ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20 | | but task is already holding lock: | ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v] | | which lock already depends on the new lock. A simple reproducer is: | #!/bin/bash | | while true; do |         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34; |         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34; | done &amp;amp; | while true; do |         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null | done Avoid this by freeing list_mutex right after deleting the element from the list, then continuing with the teardown.&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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: IDLETIMER: Fix for possible ABBA deadlock Deletion of the last rule referencing a given idletimer may happen at the same time as a read of its file in sysfs: | ====================================================== | WARNING: possible circular locking dependency detected | 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted | ------------------------------------------------------ | iptables/3303 is trying to acquire lock: | ffff8881057e04b8 (kn-&amp;gt;active#48){++++}-{0:0}, at: __kernfs_remove+0x20 | | but task is already holding lock: | ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v] | | which lock already depends on the new lock. A simple reproducer is: | #!/bin/bash | | while true; do |         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34; |         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &amp;#34;testme&amp;#34; | done &amp;amp; | while true; do |         cat /sys/class/xt_idletimer/timers/testme &amp;gt;/dev/null | done Avoid this by freeing list_mutex right after deleting the element from the list, then continuing with the teardown.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-54683</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0047 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0047</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und weitere nicht spezifizierte Angriffe zu starten.&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 und weitere nicht spezifizierte Angriffe zu starten.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0047</guid>
    </item>
  </channel>
</rss>
