CVE-2024-54683: Linux kernel · netfilter: IDLETIMER: Fix for possible ABBA deadlock
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1029.31~22.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 11:14 UTC
- Patch
- Available – fixed in 6.8.0-1029.31~22.04.1, 6.8.0-1029.34~22.04.1, 6.8.0-1030.32~22.04.1 +31
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7514-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7522-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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->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 "testme" | iptables -D INPUT -i foo -j IDLETIMER --timeout 10 --label "testme" | done & | while true; do | cat /sys/class/xt_idletimer/timers/testme >/dev/null | done Avoid this by freeing list_mutex right after deleting the element from the list, then continuing with the teardown.
References
- ubuntu.com/security/CVE-2024-54683 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-54683 (opens in a new tab)
- git.kernel.org/linus/f36b01994d68ffc253c8296e2228dfe6e6431c03 (opens in a new tab)
- git.kernel.org/stable/c/45fe76573a2557f632e248cc141342233f422b9a (opens in a new tab)
- git.kernel.org/stable/c/8c2c8445cda8f59c38dec7dc10509bcb23ae26a0 (opens in a new tab)
- git.kernel.org/stable/c/f36b01994d68ffc253c8296e2228dfe6e6431c03 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7514-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7522-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)