Look up another CVE · open CVE-2026-64178 in the interactive tracker

CVE-2026-64178

Bluetooth: bnep: Fix UAF read of dev->name

8.8 EPSS 0.2% AV:A

Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem net/bluetooth. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-64178 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

Release	Status	Version	What this means
Debian 12bookworm	fixed	6.1.176-1	Update the kernel and reboot. Fixed in 6.1.176-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixie	fixed	6.12.94-1	Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts.
Debian 14forky	fixed	7.0.12-1	Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesid	fixed	7.0.12-1	Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

bnep_add_connection() needs to keep holding the bnep_session_sem while reading dev->name (just like bnep_get_connlist() does); otherwise the bnep_session() thread can concurrently free the net_device, which can for example be triggered by a concurrent bnep_del_connection(). (This UAF is fairly uninteresting from a security perspective; calling bnep_add_connection() requires passing a capable(CAP_NET_ADMIN) check. It also requires completely tearing down a netdev during a fairly tight race window.)

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

net/bluetooth/bnep/core.c

What this is: BLUETOOTH SUBSYSTEMMAINTAINERS section matched on net/bluetooth/ · linux-bluetooth@vger.kernel.org · Supported
Kernel module: bnep

Check it on the machine

grep -wE 'CONFIG_BT|CONFIG_BT_BNEP' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w bnep

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x

M: a module where it is built at all; some flavours do not build it

Build switches: CONFIG_BT, CONFIG_BT_BNEP
Reads as: all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Debian tracker CVE record NVD kernel CNA record

Signals

Published: 2026-07-19 (3 months ago)source
CVSS: 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector: adjacent network (AV:A)source
EPSS: 0.25%, higher than 15.1% of all CVEssource
CISA KEV: not listedthe KEV catalogue
Debian urgency: not yet assignedsource
Subsystem: net/bluetooth

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
2.6.12	5.10.258	a75bbcb10cb2
2.6.12	5.15.209	4907596f25b1
2.6.12	6.1.175	915a92182e2c
2.6.12	6.6.142	fe69f634b076
2.6.12	6.12.92	b21805258d7e
2.6.12	6.18.34	5506aec79513
2.6.12	7.0.11	e7578529b97e
2.6.12	7.1	59e932ded949

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:AAttack vector, adjacent network: The bug is in BNEP session setup for Bluetooth PAN; the highest-impact scenario is an adjacent Bluetooth peer on a phone or laptop whose stack calls BNEPCONNADD during PAN bridging, not a generic local syscall path.
AC:LAttack complexity, low: The attacker controls disconnect/reconnect timing on the established L2CAP socket and can repeatedly race teardown against bnep_add_connection()'s unprotected strcpy window; UAF races with attacker-controlled concurrency are AC:L.
PR:NPrivileges required, none: Exploitation does not require attacker privileges on the victim—only adjacency as the connected Bluetooth peer while the victim's privileged bluetoothd issues BNEPCONNADD; CAP_NET_ADMIN gates the ioctl on the victim side, not the attacker.
UI:NUser interaction, none: Once Bluetooth PAN/tethering is available, the attacker initiates and tears down the connection to drive the race without requiring additional victim action during exploitation.
S:UScope, unchanged: Impact is kernel memory corruption and potential privilege escalation within the host kernel, not crossing into another security authority such as a VM guest or separate sandbox domain.
C:HConfidentiality impact, high: This is a use-after-free read of freed net_device memory via strcpy(dev->name); UAF reads can expose reclaimed slab contents and support further kernel memory disclosure.
I:HIntegrity impact, high: UAF on a heap-allocated net_device can be leveraged with heap grooming for control-flow or data corruption beyond the immediate bounded name copy.
A:HAvailability impact, high: Concurrent free of the net_device during the UAF read can cause kernel oops/panic and denial of service, consistent with UAF availability impact.