First published: Thu Nov 07 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: fix wild-memory-access in proto_unregister There's issue as follows: KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f] CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G W RIP: 0010:proto_unregister+0xee/0x400 Call Trace: <TASK> __do_sys_delete_module+0x318/0x580 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f As bnep_init() ignore bnep_sock_init()'s return value, and bnep_sock_init() will cleanup all resource. Then when remove bnep module will call bnep_sock_cleanup() to cleanup sock's resource. To solve above issue just return bnep_sock_init()'s return value in bnep_exit().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=2.6.12<4.19.323 | |
Linux Kernel | >=4.20<5.4.285 | |
Linux Kernel | >=5.5<5.10.229 | |
Linux Kernel | >=5.11<5.15.170 | |
Linux Kernel | >=5.16<6.1.115 | |
Linux Kernel | >=6.2<6.6.59 | |
Linux Kernel | >=6.7<6.11.6 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-50148 has a severity rating that indicates it could lead to potential wild memory access vulnerabilities in the Linux kernel.
To fix CVE-2024-50148, users should update their Linux kernel to a version that has addressed the vulnerability.
CVE-2024-50148 affects several Linux kernel versions including those between 2.6.12 and 4.19.323, and similar ranges for version 5.x and 6.x.
CVE-2024-50148 involves a wild memory access issue in the Bluetooth bnep protocol, which can cause instability or crashes.
Users and applications that utilize the affected versions of the Linux kernel with Bluetooth functionalities are primarily at risk from CVE-2024-50148.