Bluetooth: bnep: Fix UAF read of dev->name
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 5506aec795135cdd4cbf4e845929155663b25055| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: bnep: Fix UAF read of dev->name
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.)
From the CVE record · Linux
The Linux kernel's Bluetooth bnep code can read a network device name after the device has been freed. Triggering this requires CAP_NET_ADMIN privileges and a concurrent connection teardown during a tight race window.
Engineers running Linux kernels with the affected Bluetooth bnep code should check their kernel versions.