CVE-2024-50148
Published Nov 7, 2024
Last updated 9 days ago
Overview
- Description
- 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().
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- NVD status
- Awaiting Analysis
Social media
- Hype score
- Not currently trending
(CVE-2024-50148)[Bluetooth][bnep]wild-memory-access in proto_unregister bnep_init() ignore bnep_sock_init()'s return value and bnep_sock_init() will cleanup all resource -> remove bnep module -> bnep_sock_cleanup() cleanup sock's resource https://t.co/Jcb3EPQfps
@xvonfers
7 Nov 2024
10 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
CVE-2024-50148 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: m… https://t.co/jFXvKwV3VT
@CVEnew
7 Nov 2024
351 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes