linux-cve-announce - CVE-2025-40284: Bluetooth: MGMT: cancel mesh send timer when hdev removed

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025120718-CVE-2025-40284-9c41@gregkh>
Date: Sun,  7 Dec 2025 06:52:31 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40284: Bluetooth: MGMT: cancel mesh send timer when hdev removed

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: MGMT: cancel mesh send timer when hdev removed

mesh_send_done timer is not canceled when hdev is removed, which causes
crash if the timer triggers after hdev is gone.

Cancel the timer when MGMT removes the hdev, like other MGMT timers.

Should fix the BUG: sporadically seen by BlueZ test bot
(in "Mesh - Send cancel - 1" test).

Log:
------
BUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0
...
Freed by task 36:
 kasan_save_stack+0x24/0x50
 kasan_save_track+0x14/0x30
 __kasan_save_free_info+0x3a/0x60
 __kasan_slab_free+0x43/0x70
 kfree+0x103/0x500
 device_release+0x9a/0x210
 kobject_put+0x100/0x1e0
 vhci_release+0x18b/0x240
------

The Linux kernel CVE team has assigned CVE-2025-40284 to this issue.


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

	Issue introduced in 6.1 with commit b338d91703fae6f6afd67f3f75caa3b8f36ddef3 and fixed in 6.1.159 with commit 990e6143b0ca0c66f099d67d00c112bf59b30d76
	Issue introduced in 6.1 with commit b338d91703fae6f6afd67f3f75caa3b8f36ddef3 and fixed in 6.6.117 with commit 2927ff643607eddf4f03d10ef80fe10d977154aa
	Issue introduced in 6.1 with commit b338d91703fae6f6afd67f3f75caa3b8f36ddef3 and fixed in 6.12.59 with commit 7b6b6c077cad0601d62c3c34ab7ce3fb25deda7b
	Issue introduced in 6.1 with commit b338d91703fae6f6afd67f3f75caa3b8f36ddef3 and fixed in 6.17.9 with commit fd62ca5ad136dcf6f5aa308423b299a6be6f54ea
	Issue introduced in 6.1 with commit b338d91703fae6f6afd67f3f75caa3b8f36ddef3 and fixed in 6.18 with commit 55fb52ffdd62850d667ebed842815e072d3c9961

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-2025-40284
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/mgmt.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/990e6143b0ca0c66f099d67d00c112bf59b30d76
	https://git.kernel.org/stable/c/2927ff643607eddf4f03d10ef80fe10d977154aa
	https://git.kernel.org/stable/c/7b6b6c077cad0601d62c3c34ab7ce3fb25deda7b
	https://git.kernel.org/stable/c/fd62ca5ad136dcf6f5aa308423b299a6be6f54ea
	https://git.kernel.org/stable/c/55fb52ffdd62850d667ebed842815e072d3c9961