linux-cve-announce - CVE-2024-50148: Bluetooth: bnep: fix wild-memory-access in proto

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024110744-CVE-2024-50148-b75c@gregkh>
Date: Thu,  7 Nov 2024 10:34:48 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50148: Bluetooth: bnep: fix wild-memory-access in proto_unregister

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

The Linux kernel CVE team has assigned CVE-2024-50148 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 5.15.170 with commit fa58e23ea135
	Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.1.115 with commit 03015b6329e6
	Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.6.59 with commit d10cd7bf574e
	Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.11.6 with commit 20c424bc475b
	Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.12-rc4 with commit 64a90991ba8d

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2024-50148
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/bluetooth/bnep/core.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	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