CVE-2024-56653: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: avoid UAF in btmtk_process_coredump hci_devcd_append may lead to the release of the skb, so it cannot be accessed once it is called. ================================================================== BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk] Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82 CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c Hardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024 Workqueue: events btusb_rx_work [btusb] Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK> Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232 The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28) The buggy address belongs to the physical page: page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa head:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0x4000000000000840(slab|head|zone=1) page_type: 0xffffffff() raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001 raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb >ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Check if we need to call hci_devcd_complete before calling hci_devcd_append. That requires that we check data->cd_info.cnt >= MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as we increment data->cd_info.cnt only once the call to hci_devcd_append succeeds.
AI Analysis
Technical Summary
CVE-2024-56653 is a high-severity use-after-free (UAF) vulnerability in the Linux kernel's Bluetooth subsystem, specifically within the MediaTek Bluetooth driver component (btmtk). The flaw arises in the function btmtk_process_coredump, where improper handling of socket buffers (skbs) leads to a use-after-free condition. The vulnerability is triggered when the function hci_devcd_append releases an skb, but subsequent code attempts to access this freed memory, causing a read of invalid memory. This is confirmed by Kernel Address Sanitizer (KASAN) reports indicating slab-use-after-free errors. The root cause is a logic error in managing the lifecycle of Bluetooth core dump data structures, where the increment of a counter (data->cd_info.cnt) occurs only after a successful call to hci_devcd_append, but the check for completion uses a strict greater-than comparison instead of greater-than-or-equal, leading to premature access of freed memory. Exploitation requires local privileges (low complexity) without user interaction, and the impact includes full compromise of confidentiality, integrity, and availability of the affected system due to kernel-level memory corruption. The vulnerability affects Linux kernel versions including 6.6.40 and likely others incorporating the vulnerable btmtk driver code. No known exploits are currently reported in the wild, but the nature of the flaw and its kernel-level impact make it a critical target for attackers seeking privilege escalation or denial of service.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on Linux-based systems with Bluetooth functionality enabled, such as enterprise servers, workstations, and embedded devices. Successful exploitation could allow attackers to execute arbitrary code with kernel privileges, leading to complete system compromise, data theft, or disruption of critical services. Industries with high Bluetooth usage, including telecommunications, manufacturing (IoT devices), healthcare (medical devices), and public sector infrastructure, are particularly vulnerable. The vulnerability could also facilitate lateral movement within networks if exploited on endpoint devices. Given the widespread deployment of Linux in European data centers and critical infrastructure, the impact could extend to national security, privacy compliance (GDPR), and operational continuity. The requirement for local privileges somewhat limits remote exploitation but does not eliminate risk, as attackers could leverage other vulnerabilities or social engineering to gain initial access.
Mitigation Recommendations
European organizations should prioritize patching Linux kernels to versions that include the fix for CVE-2024-56653 as soon as updates are available from their Linux distribution vendors. Until patches are applied, organizations should: 1) Disable or restrict Bluetooth functionality on systems where it is not essential, especially on critical servers and endpoints. 2) Implement strict access controls and monitoring to prevent unauthorized local access, including hardened user privilege management and use of endpoint detection and response (EDR) tools to detect suspicious kernel activity. 3) Employ kernel hardening techniques such as Kernel Address Space Layout Randomization (KASLR) and enable Kernel Page Table Isolation (KPTI) to reduce exploitation likelihood. 4) Conduct thorough audits of devices with MediaTek Bluetooth chipsets to identify vulnerable systems. 5) Educate users on the risks of local privilege escalation and enforce policies to limit installation of untrusted software that could be used to exploit this vulnerability. 6) Monitor security advisories and threat intelligence feeds for any emerging exploit attempts targeting this CVE.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Finland, Poland
CVE-2024-56653: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: avoid UAF in btmtk_process_coredump hci_devcd_append may lead to the release of the skb, so it cannot be accessed once it is called. ================================================================== BUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk] Read of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82 CPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G U 6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c Hardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024 Workqueue: events btusb_rx_work [btusb] Call Trace: <TASK> dump_stack_lvl+0xfd/0x150 print_report+0x131/0x780 kasan_report+0x177/0x1c0 btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01] btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 </TASK> Allocated by task 82: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 __kasan_slab_alloc+0x4e/0x60 kmem_cache_alloc+0x19f/0x360 skb_clone+0x132/0xf70 btusb_recv_acl_mtk+0x104/0x1a0 [btusb] btusb_rx_work+0x9e/0xe0 [btusb] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 Freed by task 1733: stack_trace_save+0xdc/0x190 kasan_set_track+0x4e/0x80 kasan_save_free_info+0x28/0xb0 ____kasan_slab_free+0xfd/0x170 kmem_cache_free+0x183/0x3f0 hci_devcd_rx+0x91a/0x2060 [bluetooth] worker_thread+0xe44/0x2cc0 kthread+0x2ff/0x3a0 ret_from_fork+0x51/0x80 ret_from_fork_asm+0x1b/0x30 The buggy address belongs to the object at ffff888033cfab40 which belongs to the cache skbuff_head_cache of size 232 The buggy address is located 112 bytes inside of freed 232-byte region [ffff888033cfab40, ffff888033cfac28) The buggy address belongs to the physical page: page:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa head:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0 anon flags: 0x4000000000000840(slab|head|zone=1) page_type: 0xffffffff() raw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001 raw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb >ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Check if we need to call hci_devcd_complete before calling hci_devcd_append. That requires that we check data->cd_info.cnt >= MTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as we increment data->cd_info.cnt only once the call to hci_devcd_append succeeds.
AI-Powered Analysis
Technical Analysis
CVE-2024-56653 is a high-severity use-after-free (UAF) vulnerability in the Linux kernel's Bluetooth subsystem, specifically within the MediaTek Bluetooth driver component (btmtk). The flaw arises in the function btmtk_process_coredump, where improper handling of socket buffers (skbs) leads to a use-after-free condition. The vulnerability is triggered when the function hci_devcd_append releases an skb, but subsequent code attempts to access this freed memory, causing a read of invalid memory. This is confirmed by Kernel Address Sanitizer (KASAN) reports indicating slab-use-after-free errors. The root cause is a logic error in managing the lifecycle of Bluetooth core dump data structures, where the increment of a counter (data->cd_info.cnt) occurs only after a successful call to hci_devcd_append, but the check for completion uses a strict greater-than comparison instead of greater-than-or-equal, leading to premature access of freed memory. Exploitation requires local privileges (low complexity) without user interaction, and the impact includes full compromise of confidentiality, integrity, and availability of the affected system due to kernel-level memory corruption. The vulnerability affects Linux kernel versions including 6.6.40 and likely others incorporating the vulnerable btmtk driver code. No known exploits are currently reported in the wild, but the nature of the flaw and its kernel-level impact make it a critical target for attackers seeking privilege escalation or denial of service.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on Linux-based systems with Bluetooth functionality enabled, such as enterprise servers, workstations, and embedded devices. Successful exploitation could allow attackers to execute arbitrary code with kernel privileges, leading to complete system compromise, data theft, or disruption of critical services. Industries with high Bluetooth usage, including telecommunications, manufacturing (IoT devices), healthcare (medical devices), and public sector infrastructure, are particularly vulnerable. The vulnerability could also facilitate lateral movement within networks if exploited on endpoint devices. Given the widespread deployment of Linux in European data centers and critical infrastructure, the impact could extend to national security, privacy compliance (GDPR), and operational continuity. The requirement for local privileges somewhat limits remote exploitation but does not eliminate risk, as attackers could leverage other vulnerabilities or social engineering to gain initial access.
Mitigation Recommendations
European organizations should prioritize patching Linux kernels to versions that include the fix for CVE-2024-56653 as soon as updates are available from their Linux distribution vendors. Until patches are applied, organizations should: 1) Disable or restrict Bluetooth functionality on systems where it is not essential, especially on critical servers and endpoints. 2) Implement strict access controls and monitoring to prevent unauthorized local access, including hardened user privilege management and use of endpoint detection and response (EDR) tools to detect suspicious kernel activity. 3) Employ kernel hardening techniques such as Kernel Address Space Layout Randomization (KASLR) and enable Kernel Page Table Isolation (KPTI) to reduce exploitation likelihood. 4) Conduct thorough audits of devices with MediaTek Bluetooth chipsets to identify vulnerable systems. 5) Educate users on the risks of local privilege escalation and enforce policies to limit installation of untrusted software that could be used to exploit this vulnerability. 6) Monitor security advisories and threat intelligence feeds for any emerging exploit attempts targeting this CVE.
Affected Countries
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-12-27T15:00:39.841Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9822c4522896dcbde472
Added to database: 5/21/2025, 9:08:50 AM
Last enriched: 7/2/2025, 10:09:47 PM
Last updated: 8/13/2025, 12:34:04 PM
Views: 11
Related Threats
CVE-2025-9026: OS Command Injection in D-Link DIR-860L
MediumCVE-2025-9025: SQL Injection in code-projects Simple Cafe Ordering System
MediumCVE-2025-9024: SQL Injection in PHPGurukul Beauty Parlour Management System
MediumCVE-2025-9023: Buffer Overflow in Tenda AC7
HighCVE-2025-8905: CWE-94 Improper Control of Generation of Code ('Code Injection') in inpersttion Inpersttion For Theme
MediumActions
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.