{"uuid": "0086611b-0c8c-41f1-a23f-4f9665c99f2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-54683", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/15077", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-54683 - Linux Kernel netfilter IDLETIMER Locking Dependency Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-54683 \nPublished : Jan. 11, 2025, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: IDLETIMER: Fix for possible ABBA deadlock  \n  \nDeletion of the last rule referencing a given idletimer may happen at  \nthe same time as a read of its file in sysfs:  \n  \n| ======================================================  \n| WARNING: possible circular locking dependency detected  \n| 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted  \n| ------------------------------------------------------  \n| iptables/3303 is trying to acquire lock:  \n| ffff8881057e04b8 (kn->active#48){++++}-{0:0}, at: __kernfs_remove+0x20  \n|  \n| but task is already holding lock:  \n| ffffffffa0249068 (list_mutex){+.+.}-{3:3}, at: idletimer_tg_destroy_v]  \n|  \n| which lock already depends on the new lock.  \n  \nA simple reproducer is:  \n  \n| #!/bin/bash  \n|  \n| while true; do  \n|         iptables -A INPUT -i foo -j IDLETIMER --timeout 10 --label \"testme\"  \n|         iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label \"testme\"  \n| done &  \n| while true; do  \n|         cat /sys/class/xt_idletimer/timers/testme >/dev/null  \n| done  \n  \nAvoid this by freeing list_mutex right after deleting the element from  \nthe list, then continuing with the teardown. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-11T14:55:33.000000Z"}