CVE-2026-64434

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_f

What this means for your business

It affects Linux Kernel. It matters if your company, or a supplier that handles your data, runs it.
An attacker can use it from inside the same network, without a login, and without anyone at your company clicking anything.
FIRST's prediction model gives it a 0.4% chance of attack attempts being seen in the next 30 days, ranking above 31% of all known flaws.

What to do

1Check whether your company or your suppliers run Linux Kernel, and which version. The affected versions are listed further down this page.
2If you do, apply the vendor's fix. A patch or vendor advisory has been published.

Fastnexa security experts

Not sure if your company is exposed to CVE-2026-64434?

Tell us where you run Linux Linux Kernel and a Fastnexa penetration tester will check whether this flaw, or others like it, can be used against your websites, apps and network.

The full test is free for our first 10 founding clients until 31 December 2026. See the offer

Book a 30-min call WhatsApp us

Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →

Scoring

CVSS: 8.8 (v3.1)
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-416
Assigned by: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Dates

Published: 2026-07-25
Last modified: 2026-09-03
Sources: NVD

Affected products

Linux Linux Kernel5.10.259 - 5.10.265, 5.15.210 - 5.15.216, 6.1.176 - 6.1.183, 6.6.143 - 6.6.145, 6.12.93 - 6.12.97, 6.18.35 - 6.18.39, 7.0.12 - 7.1, 7.1.1 - 7.1.4, 7.1

As listed in the NVD configuration data. Not a statement about your estate.