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().

kernel.org https://git.kernel.org/stable/c/03015b6329e6de42f03ec917c25c4cf944f81f66 [No types assigned]

kernel.org https://git.kernel.org/stable/c/20c424bc475b2b2a6e0e2225d2aae095c2ab2f41 [No types assigned]

kernel.org https://git.kernel.org/stable/c/64a90991ba8d4e32e3173ddd83d0b24167a5668c [No types assigned]

kernel.org https://git.kernel.org/stable/c/d10cd7bf574ead01fae140ce117a11bcdacbe6a8 [No types assigned]

kernel.org https://git.kernel.org/stable/c/fa58e23ea1359bd24b323916d191e2e9b4b19783 [No types assigned]