CVE-2024-50148: Bluetooth: bnep: fix wild-memory-access in proto_unregister
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: bnep: fix wild-memory-access in protounregister
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:protounregister+0xee/0x400 Call Trace: <TASK> dosysdeletemodule+0x318/0x580 dosyscall64+0xc1/0x1d0 entrySYSCALL64afterhwframe+0x77/0x7f
As bnepinit() ignore bnepsockinit()'s return value, and bnepsockinit() will cleanup all resource. Then when remove bnep module will call bnepsockcleanup() to cleanup sock's resource. To solve above issue just return bnepsockinit()'s return value in bnepexit().
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50148?
CVE-2024-50148 has a severity rating that indicates it could lead to potential wild memory access vulnerabilities in the Linux kernel.
How do I fix CVE-2024-50148?
To fix CVE-2024-50148, users should update their Linux kernel to a version that has addressed the vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50148?
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.
What is the nature of the vulnerability in CVE-2024-50148?
CVE-2024-50148 involves a wild memory access issue in the Bluetooth bnep protocol, which can cause instability or crashes.
Who is primarily impacted by CVE-2024-50148?
Users and applications that utilize the affected versions of the Linux kernel with Bluetooth functionalities are primarily at risk from CVE-2024-50148.