---
id: CVE-2024-50148
title: |-
  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 U…
summary: |-
  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 U…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 2.6.12, < 4.19.323'
  - 'linux_kernel >= 4.20, < 5.4.285'
  - 'linux_kernel >= 5.5, < 5.10.229'
  - 'linux_kernel >= 5.11, < 5.15.170'
  - 'linux_kernel >= 5.16, < 6.1.115'
  - 'linux_kernel >= 6.2, < 6.6.59'
  - 'linux_kernel >= 6.7, < 6.11.6'
  - linux_kernel = 6.12
patched:
  - linux_kernel 6.11.6
published: '2024-11-07'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T01:19:08.410'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-50148'
references:
  - url: 'https://git.kernel.org/stable/c/03015b6329e6de42f03ec917c25c4cf944f81f66'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/20c424bc475b2b2a6e0e2225d2aae095c2ab2f41'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2c439470b23d78095a0d2f923342df58b155f669'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/64a90991ba8d4e32e3173ddd83d0b24167a5668c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6c151aeb6dc414db8f4daf51be072e802fae6667'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d10cd7bf574ead01fae140ce117a11bcdacbe6a8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e232728242c4e98fb30e4c6bedb6ba8b482b6301'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fa58e23ea1359bd24b323916d191e2e9b4b19783'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00262
epssPercentile: 0.17888
ingestedAt: '2026-10-15T03:30:12.764Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2025-10-01T20:20:47.201820Z'
---

## Overview

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

## Affected

- `linux_kernel >= 2.6.12, < 4.19.323`
- `linux_kernel >= 4.20, < 5.4.285`
- `linux_kernel >= 5.5, < 5.10.229`
- `linux_kernel >= 5.11, < 5.15.170`
- `linux_kernel >= 5.16, < 6.1.115`
- `linux_kernel >= 6.2, < 6.6.59`
- `linux_kernel >= 6.7, < 6.11.6`
- `linux_kernel = 6.12`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.11.6`