CVE-2024-50078

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Call iso_exit() on module unload If iso_init() has been called, iso_exit() must be called on module unload. Without that, the struct proto that iso_init() registered with proto_register() becomes invalid, which could cause unpredictable problems later. In my case, with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, loading the module again usually triggers this BUG(): list_add corruption. next->prev should be prev (ffffffffb5355fd0), but was 0000000000000068. (next=ffffffffc0a010d0). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:29! Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 4159 Comm: modprobe Not tainted 6.10.11-4+bt2-ao-desktop #1 RIP: 0010:__list_add_valid_or_report+0x61/0xa0 ... __list_add_valid_or_report+0x61/0xa0 proto_register+0x299/0x320 hci_sock_init+0x16/0xc0 [bluetooth] bt_init+0x68/0xd0 [bluetooth] __pfx_bt_init+0x10/0x10 [bluetooth] do_one_initcall+0x80/0x2f0 do_init_module+0x8b/0x230 __do_sys_init_module+0x15f/0x190 do_syscall_64+0x68/0x110 ...
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*

History

01 Nov 2024, 16:01

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/05f84d86169b2ebac185c5736a256823d42c425b - () https://git.kernel.org/stable/c/05f84d86169b2ebac185c5736a256823d42c425b - Patch
References () https://git.kernel.org/stable/c/4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a - () https://git.kernel.org/stable/c/4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a - Patch
References () https://git.kernel.org/stable/c/d458cd1221e9e56da3b2cc5518ad3225caa91f20 - () https://git.kernel.org/stable/c/d458cd1221e9e56da3b2cc5518ad3225caa91f20 - Patch
References () https://git.kernel.org/stable/c/f905a7d95091e0d2605a3a1a157a9351f09ab2e1 - () https://git.kernel.org/stable/c/f905a7d95091e0d2605a3a1a157a9351f09ab2e1 - Patch
CPE cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
CWE NVD-CWE-noinfo
First Time Linux
Linux linux Kernel
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5

29 Oct 2024, 14:34

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: Bluetooth: Llamada a iso_exit() en la descarga del módulo Si se ha llamado a iso_init(), se debe llamar a iso_exit() en la descarga del módulo. Sin eso, el struct proto que iso_init() registró con proto_register() se vuelve inválido, lo que podría causar problemas impredecibles más adelante. En mi caso, con CONFIG_LIST_HARDENED y CONFIG_BUG_ON_DATA_CORRUPTION habilitados, cargar el módulo nuevamente generalmente desencadena este BUG(): corrupción de list_add. next->prev debería ser prev (ffffffffb5355fd0), pero era 0000000000000068. (next=ffffffffc0a010d0). ------------[ cortar aquí ]------------ ¡ERROR del kernel en lib/list_debug.c:29! Ups: código de operación no válido: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 4159 Comm: modprobe No contaminado 6.10.11-4+bt2-ao-desktop #1 RIP: 0010:__list_add_valid_or_report+0x61/0xa0 ... __list_add_valid_or_report+0x61/0xa0 proto_register+0x299/0x320 hci_sock_init+0x16/0xc0 [bluetooth] bt_init+0x68/0xd0 [bluetooth] __pfx_bt_init+0x10/0x10 [bluetooth] do_one_initcall+0x80/0x2f0 do_init_module+0x8b/0x230 __do_sys_init_module+0x15f/0x190 hacer_llamada_al_sistema_64+0x68/0x110 ...

29 Oct 2024, 01:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-10-29 01:15

Updated : 2024-11-01 16:01


NVD link : CVE-2024-50078

Mitre link : CVE-2024-50078

CVE.ORG link : CVE-2024-50078


JSON object : View

Products Affected

linux

  • linux_kernel