https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 06:55:28 +0000 https://vulnerability.circl.lu/vuln/cve-2024-54683 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfilter: IDLETIMER: Fix for possible ABBA deadlock</p> <p>Deletion of the last rule referencing a given idletimer may happen at the same time as a read of its file in sysfs:</p> <p>| ====================================================== | 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-&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.</p> <p>A simple reproducer is:</p> <p>| #!/bin/bash | | while true; do | iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &#34;testme&#34; | iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &#34;testme&#34; | done &amp; | while true; do | cat /sys/class/xt_idletimer/timers/testme &gt;/dev/null | done</p> <p>Avoid this by freeing list_mutex right after deleting the element from the list, then continuing with the teardown.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfilter: IDLETIMER: Fix for possible ABBA deadlock</p> <p>Deletion of the last rule referencing a given idletimer may happen at the same time as a read of its file in sysfs:</p> <p>| ====================================================== | 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-&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.</p> <p>A simple reproducer is:</p> <p>| #!/bin/bash | | while true; do | iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label &#34;testme&#34; | iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label &#34;testme&#34; | done &amp; | while true; do | cat /sys/class/xt_idletimer/timers/testme &gt;/dev/null | done</p> <p>Avoid this by freeing list_mutex right after deleting the element from the list, then continuing with the teardown.</p> https://vulnerability.circl.lu/vuln/cve-2024-54683