Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 15f02b91056253e8cdc592888f431da0731337b8 · < f39049304ba655ffcbb92edbdf8c51a1f1210bed| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success
l2cap_ecred_reconf_rsp() returns early on success without clearing chan->ident. Every other L2CAP response handler (l2cap_ecred_conn_rsp, l2cap_le_connect_rsp, l2cap_config_rsp) clears chan->ident after a successful transaction to prevent the channel from matching subsequent responses with the recycled ident value.
A remote attacker that completed a reconfiguration as the peer can replay a failure response with the stale ident, causing the kernel to match and destroy the already-established channel via l2cap_chan_del(chan, ECONNRESET).
Clear chan->ident for all matching channels on success, and harden the failure path by using l2cap_chan_hold_unless_zero() consistent with other L2CAP handlers (l2cap_le_command_rej, __l2cap_get_chan_by_ident).
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP ECRED response handler leaves a channel identifier uncleared after a successful reconfiguration. A remote attacker acting as the peer can then replay a failure response with that identifier, causing the kernel to destroy the established channel. The attack requires the peer to have completed a reconfiguration; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with Bluetooth L2CAP should check whether their kernel is affected; affected versions were not provided.