Heimdall Security Logo

CVE-2024-53237

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : 6.13, <=6.1.*, <=6.12.*, <=6.11.*, <6.1.120, 4.19.300, 0, 6.1.120, 6.1.64, 6.5.13, <7b277bd569bb6a2777f0014f84b4344f444fd49d, a85fb91e3d728bdfc80833167e8162cce8bc7004, 5.10.231, 5.4.297, 87624b1f9b781549e69f92db7ede012a21cec275, 5.15.174, 6.6.64, 6.12.2, 56a4fdde95ed98d864611155f6728983e199e198, 5.10.202, 5.15.140, <6.6, <4.20, <de5a44f351ca7efd9add9851b218f5353e2224b7, 6.6.3, <=5.10.*, <=6.6.*, <6894717a1ea363c5a27010ba604f957c309d282d, 3c4236f1b2a715e878a06599fa8b0cc21f165d28, <6.6.64, 5c53afc766e07098429520b7677eaa164b593451, <27aabf27fd014ae037cc179c61b0bee7cff55b3d, <a9584c897d1cba6265c78010bbb45ca5722c88bc, <=5.4.*, <5.15.174, <5.4.297, ba7088769800d9892a7e4f35c3137a5b3e65410b, <0f67ca2a80acf8b207240405b7f72d660665d3df, 6.11.11, <5.10.231, <6.7, <fb91ce37dc9a37ea23cf32b6d7b667004e93d4c5, <91e2a2e4d1336333804cd31162984f01ad8cc70f, fc666d1b47518a18519241cae213de1babd4a4ba, <=*, <=5.15.*, 5.4.262, 6.7, 53d61daf35b1bbf3ae06e852ee107aa2f05b3776

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.

Gravité et risque d'exploitation

CVE-2024-53237 obtient un score CVSS de 8.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.32 %, ce qui la place devant 23.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.13, <=6.1.*, <=6.12.*, <=6.11.*, <6.1.120, 4.19.300, 0, 6.1.120, 6.1.64, 6.5.13, <7b277bd569bb6a2777f0014f84b4344f444fd49d, a85fb91e3d728bdfc80833167e8162cce8bc7004, 5.10.231, 5.4.297, 87624b1f9b781549e69f92db7ede012a21cec275, 5.15.174, 6.6.64, 6.12.2, 56a4fdde95ed98d864611155f6728983e199e198, 5.10.202, 5.15.140, <6.6, <4.20, <de5a44f351ca7efd9add9851b218f5353e2224b7, 6.6.3, <=5.10.*, <=6.6.*, <6894717a1ea363c5a27010ba604f957c309d282d, 3c4236f1b2a715e878a06599fa8b0cc21f165d28, <6.6.64, 5c53afc766e07098429520b7677eaa164b593451, <27aabf27fd014ae037cc179c61b0bee7cff55b3d, <a9584c897d1cba6265c78010bbb45ca5722c88bc, <=5.4.*, <5.15.174, <5.4.297, ba7088769800d9892a7e4f35c3137a5b3e65410b, <0f67ca2a80acf8b207240405b7f72d660665d3df, 6.11.11, <5.10.231, <6.7, <fb91ce37dc9a37ea23cf32b6d7b667004e93d4c5, <91e2a2e4d1336333804cd31162984f01ad8cc70f, fc666d1b47518a18519241cae213de1babd4a4ba, <=*, <=5.15.*, 5.4.262, 6.7, 53d61daf35b1bbf3ae06e852ee107aa2f05b3776) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE