CVE-2024-53237: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix use-after-free in device_for_each_child() Syzbot has reported the following KASAN splat: BUG: KASAN: slab-use-after-free in device_for_each_child+0x18f/0x1a0 Read of size 8 at addr ffff88801f605308 by task kbnepd bnep0/4980 CPU: 0 UID: 0 PID: 4980 Comm: kbnepd bnep0 Not tainted 6.12.0-rc4-00161-gae90f6a6170d #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x100/0x190 ? device_for_each_child+0x18f/0x1a0 print_report+0x13a/0x4cb ? __virt_addr_valid+0x5e/0x590 ? __phys_addr+0xc6/0x150 ? device_for_each_child+0x18f/0x1a0 kasan_report+0xda/0x110 ? device_for_each_child+0x18f/0x1a0 ? __pfx_dev_memalloc_noio+0x10/0x10 device_for_each_child+0x18f/0x1a0 ? __pfx_device_for_each_child+0x10/0x10 pm_runtime_set_memalloc_noio+0xf2/0x180 netdev_unregister_kobject+0x1ed/0x270 unregister_netdevice_many_notify+0x123c/0x1d80 ? __mutex_trylock_common+0xde/0x250 ? __pfx_unregister_netdevice_many_notify+0x10/0x10 ? trace_contention_end+0xe6/0x140 ? __mutex_lock+0x4e7/0x8f0 ? __pfx_lock_acquire.part.0+0x10/0x10 ? rcu_is_watching+0x12/0xc0 ? unregister_netdev+0x12/0x30 unregister_netdevice_queue+0x30d/0x3f0 ? __pfx_unregister_netdevice_queue+0x10/0x10 ? __pfx_down_write+0x10/0x10 unregister_netdev+0x1c/0x30 bnep_session+0x1fb3/0x2ab0 ? __pfx_bnep_session+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? __pfx_woken_wake_function+0x10/0x10 ? __kthread_parkme+0x132/0x200 ? __pfx_bnep_session+0x10/0x10 ? kthread+0x13a/0x370 ? __pfx_bnep_session+0x10/0x10 kthread+0x2b7/0x370 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x48/0x80 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 4974: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_noprof+0x1d1/0x440 hci_alloc_dev_priv+0x1d/0x2820 __vhci_create_device+0xef/0x7d0 vhci_write+0x2c7/0x480 vfs_write+0x6a0/0xfc0 ksys_write+0x12f/0x260 do_syscall_64+0xc7/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 4979: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x4f/0x70 kfree+0x141/0x490 hci_release_dev+0x4d9/0x600 bt_host_release+0x6a/0xb0 device_release+0xa4/0x240 kobject_put+0x1ec/0x5a0 put_device+0x1f/0x30 vhci_release+0x81/0xf0 __fput+0x3f6/0xb30 task_work_run+0x151/0x250 do_exit+0xa79/0x2c30 do_group_exit+0xd5/0x2a0 get_signal+0x1fcd/0x2210 arch_do_signal_or_restart+0x93/0x780 syscall_exit_to_user_mode+0x140/0x290 do_syscall_64+0xd4/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f In 'hci_conn_del_sysfs()', 'device_unregister()' may be called when an underlying (kobject) reference counter is greater than 1. This means that reparenting (happened when the device is actually freed) is delayed and, during that delay, parent controller device (hciX) may be deleted. Since the latter may create a dangling pointer to freed parent, avoid that scenario by reparenting to NULL explicitly.
AI Analysis
Technical Summary
CVE-2024-53237 is a high-severity use-after-free vulnerability identified in the Linux kernel's Bluetooth subsystem, specifically within the device_for_each_child() function. The vulnerability arises due to improper handling of device reference counts during device unregistration and reparenting in the hci_conn_del_sysfs() function. When device_unregister() is called, the underlying kobject reference counter may remain greater than one, delaying reparenting and causing the parent controller device (hciX) to be deleted prematurely. This leads to a dangling pointer referencing freed memory, resulting in a use-after-free condition. The kernel's Kernel Address Sanitizer (KASAN) detected this issue as a slab-use-after-free error triggered by the Bluetooth Network Encapsulation Protocol daemon (kbnepd) task. The vulnerability affects multiple Linux kernel versions prior to the patch and is triggered during Bluetooth device removal and network device unregistration processes. Exploitation requires local privileges (PR:L) but no user interaction (UI:N), and the attack vector is local (AV:L). The impact includes high confidentiality, integrity, and availability consequences due to potential arbitrary code execution or kernel crashes. The vulnerability is classified under CWE-416 (Use After Free). Although no known exploits are reported in the wild yet, the nature of the flaw and its presence in the widely used Linux kernel Bluetooth stack make it a critical issue to address promptly.
Potential Impact
For European organizations, this vulnerability poses significant risks, especially those relying on Linux-based systems with Bluetooth capabilities, such as enterprise servers, IoT devices, embedded systems, and workstations. Successful exploitation could allow an attacker with local access to execute arbitrary code in kernel context, leading to privilege escalation, data breaches, or denial of service through system crashes. This is particularly concerning for sectors like manufacturing, healthcare, telecommunications, and critical infrastructure where Linux is prevalent. The high impact on confidentiality, integrity, and availability could disrupt operations, compromise sensitive data, and undermine trust in IT systems. Additionally, the vulnerability could be leveraged in targeted attacks against organizations with Bluetooth-enabled Linux devices, increasing the threat landscape for European entities.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to the latest patched versions that address CVE-2024-53237. Given the complexity of the Bluetooth subsystem, it is advisable to audit and restrict local user privileges to minimize the risk of exploitation. Specific mitigation steps include: 1) Deploy kernel updates from trusted Linux distributions promptly; 2) Disable or restrict Bluetooth services on systems where it is not essential; 3) Implement strict access controls and monitoring for local user activities, especially on devices with Bluetooth capabilities; 4) Use kernel hardening features such as Kernel Address Sanitizer (KASAN) in testing environments to detect similar issues early; 5) Conduct regular vulnerability assessments focusing on Bluetooth and kernel subsystems; 6) For embedded or IoT devices, coordinate with vendors to ensure timely firmware updates incorporating the patch; 7) Educate system administrators about the risks of local privilege escalation vulnerabilities and the importance of patch management.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland, Belgium
CVE-2024-53237: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix use-after-free in device_for_each_child() Syzbot has reported the following KASAN splat: BUG: KASAN: slab-use-after-free in device_for_each_child+0x18f/0x1a0 Read of size 8 at addr ffff88801f605308 by task kbnepd bnep0/4980 CPU: 0 UID: 0 PID: 4980 Comm: kbnepd bnep0 Not tainted 6.12.0-rc4-00161-gae90f6a6170d #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x100/0x190 ? device_for_each_child+0x18f/0x1a0 print_report+0x13a/0x4cb ? __virt_addr_valid+0x5e/0x590 ? __phys_addr+0xc6/0x150 ? device_for_each_child+0x18f/0x1a0 kasan_report+0xda/0x110 ? device_for_each_child+0x18f/0x1a0 ? __pfx_dev_memalloc_noio+0x10/0x10 device_for_each_child+0x18f/0x1a0 ? __pfx_device_for_each_child+0x10/0x10 pm_runtime_set_memalloc_noio+0xf2/0x180 netdev_unregister_kobject+0x1ed/0x270 unregister_netdevice_many_notify+0x123c/0x1d80 ? __mutex_trylock_common+0xde/0x250 ? __pfx_unregister_netdevice_many_notify+0x10/0x10 ? trace_contention_end+0xe6/0x140 ? __mutex_lock+0x4e7/0x8f0 ? __pfx_lock_acquire.part.0+0x10/0x10 ? rcu_is_watching+0x12/0xc0 ? unregister_netdev+0x12/0x30 unregister_netdevice_queue+0x30d/0x3f0 ? __pfx_unregister_netdevice_queue+0x10/0x10 ? __pfx_down_write+0x10/0x10 unregister_netdev+0x1c/0x30 bnep_session+0x1fb3/0x2ab0 ? __pfx_bnep_session+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? __pfx_woken_wake_function+0x10/0x10 ? __kthread_parkme+0x132/0x200 ? __pfx_bnep_session+0x10/0x10 ? kthread+0x13a/0x370 ? __pfx_bnep_session+0x10/0x10 kthread+0x2b7/0x370 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x48/0x80 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 4974: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_noprof+0x1d1/0x440 hci_alloc_dev_priv+0x1d/0x2820 __vhci_create_device+0xef/0x7d0 vhci_write+0x2c7/0x480 vfs_write+0x6a0/0xfc0 ksys_write+0x12f/0x260 do_syscall_64+0xc7/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 4979: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x4f/0x70 kfree+0x141/0x490 hci_release_dev+0x4d9/0x600 bt_host_release+0x6a/0xb0 device_release+0xa4/0x240 kobject_put+0x1ec/0x5a0 put_device+0x1f/0x30 vhci_release+0x81/0xf0 __fput+0x3f6/0xb30 task_work_run+0x151/0x250 do_exit+0xa79/0x2c30 do_group_exit+0xd5/0x2a0 get_signal+0x1fcd/0x2210 arch_do_signal_or_restart+0x93/0x780 syscall_exit_to_user_mode+0x140/0x290 do_syscall_64+0xd4/0x250 entry_SYSCALL_64_after_hwframe+0x77/0x7f In 'hci_conn_del_sysfs()', 'device_unregister()' may be called when an underlying (kobject) reference counter is greater than 1. This means that reparenting (happened when the device is actually freed) is delayed and, during that delay, parent controller device (hciX) may be deleted. Since the latter may create a dangling pointer to freed parent, avoid that scenario by reparenting to NULL explicitly.
AI-Powered Analysis
Technical Analysis
CVE-2024-53237 is a high-severity use-after-free vulnerability identified in the Linux kernel's Bluetooth subsystem, specifically within the device_for_each_child() function. The vulnerability arises due to improper handling of device reference counts during device unregistration and reparenting in the hci_conn_del_sysfs() function. When device_unregister() is called, the underlying kobject reference counter may remain greater than one, delaying reparenting and causing the parent controller device (hciX) to be deleted prematurely. This leads to a dangling pointer referencing freed memory, resulting in a use-after-free condition. The kernel's Kernel Address Sanitizer (KASAN) detected this issue as a slab-use-after-free error triggered by the Bluetooth Network Encapsulation Protocol daemon (kbnepd) task. The vulnerability affects multiple Linux kernel versions prior to the patch and is triggered during Bluetooth device removal and network device unregistration processes. Exploitation requires local privileges (PR:L) but no user interaction (UI:N), and the attack vector is local (AV:L). The impact includes high confidentiality, integrity, and availability consequences due to potential arbitrary code execution or kernel crashes. The vulnerability is classified under CWE-416 (Use After Free). Although no known exploits are reported in the wild yet, the nature of the flaw and its presence in the widely used Linux kernel Bluetooth stack make it a critical issue to address promptly.
Potential Impact
For European organizations, this vulnerability poses significant risks, especially those relying on Linux-based systems with Bluetooth capabilities, such as enterprise servers, IoT devices, embedded systems, and workstations. Successful exploitation could allow an attacker with local access to execute arbitrary code in kernel context, leading to privilege escalation, data breaches, or denial of service through system crashes. This is particularly concerning for sectors like manufacturing, healthcare, telecommunications, and critical infrastructure where Linux is prevalent. The high impact on confidentiality, integrity, and availability could disrupt operations, compromise sensitive data, and undermine trust in IT systems. Additionally, the vulnerability could be leveraged in targeted attacks against organizations with Bluetooth-enabled Linux devices, increasing the threat landscape for European entities.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to the latest patched versions that address CVE-2024-53237. Given the complexity of the Bluetooth subsystem, it is advisable to audit and restrict local user privileges to minimize the risk of exploitation. Specific mitigation steps include: 1) Deploy kernel updates from trusted Linux distributions promptly; 2) Disable or restrict Bluetooth services on systems where it is not essential; 3) Implement strict access controls and monitoring for local user activities, especially on devices with Bluetooth capabilities; 4) Use kernel hardening features such as Kernel Address Sanitizer (KASAN) in testing environments to detect similar issues early; 5) Conduct regular vulnerability assessments focusing on Bluetooth and kernel subsystems; 6) For embedded or IoT devices, coordinate with vendors to ensure timely firmware updates incorporating the patch; 7) Educate system administrators about the risks of local privilege escalation vulnerabilities and the importance of patch management.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-11-19T17:17:25.026Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9820c4522896dcbdd094
Added to database: 5/21/2025, 9:08:48 AM
Last enriched: 7/3/2025, 2:13:59 PM
Last updated: 7/31/2025, 4:20:41 AM
Views: 9
Related Threats
CVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9087: Stack-based Buffer Overflow in Tenda AC20
HighTop Israeli Cybersecurity Director Arrested in US Child Exploitation Sting
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.