Bluetooth: bnep: fix wild-memory-access in proto_unregister
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < d10cd7bf574ead01fae140ce117a11bcdacbe6a8| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel’s Bluetooth BNEP code can trigger a wild memory access during module removal if BNEP socket initialization fails and its return value is ignored. The reported issue occurs locally when the BNEP module is removed; the input does not establish whether an attacker can trigger it or what access they would need.
Engineers running Linux kernels with the Bluetooth BNEP module should check their versions against the vendor advisory; affected versions were not specified.