Bluetooth: bnep: pin L2CAP connection during netdev registration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 65f53e9802dbfae0e5758a91793c3f5f8bece49b · < a6b22dbd80926556290ad2243be25218d6956a19| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: bnep: pin L2CAP connection during netdev registration
bnep_add_connection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and release that connection concurrently, leaving the network device registration path to dereference a freed parent device.
Take a reference to the L2CAP connection while holding the channel lock. Retain it until register_netdev() has taken the parent device reference.
From the CVE record · Linux
The Linux kernel's Bluetooth bnep code can use a freed L2CAP connection during network device registration if controller teardown happens concurrently. This can cause the registration path to dereference a freed parent device. The input does not specify how an attacker could trigger this condition or whether authentication or user interaction is required.
Engineers running Linux kernels with Bluetooth bnep should check their versions; affected versions are not specified.