Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4.20, Kernel 4.5, Kernel 4.10 and 17 more.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop l2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED state to support L2CAP reconfiguration (e.g. MTU changes). However, since both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from the initial configuration, the reconfiguration path falls through to l2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and retrans_list without freeing the previous allocations and sets chan->sdu to NULL without freeing the existing skb. This leaks all previously allocated ERTM resources. Additionally, l2cap_parse_conf_req() does not validate the minimum value of remote_mps derived from the RFC max_pdu_size option. A zero value propagates to l2cap_segment_sdu() where pdu_len becomes zero, causing the while loop to never terminate since len is never decremented, exhausting all available memory. Fix the double-init by skipping l2cap_ertm_init() and l2cap_chan_ready() when the channel is already in BT_CONNECTED state, while still allowing the reconfiguration parameters to be updated through l2cap_parse_conf_req(). Also add a pdu_len zero check in l2cap_segment_sdu() as a safeguard.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.7, >=4.19.149 <4.20, >=4.4.238 <4.5, >=4.9.238 <4.10, >=5.11 <5.15.203, >=5.16 <6.1.168, >=5.4.69 <5.5, >=5.7.1 <5.10.253, >=6.13 <6.18.21, >=6.19 <6.19.11, >=6.2 <6.6.131, >=6.7 <6.12.80, >=4.14.200 <4.15, =7.0, >=96298f640104e4cd9a913a6e50b0b981829b94ff <042e2cd4bb11e5313b19b87593616524949e4c52, >=96298f640104e4cd9a913a6e50b0b981829b94ff <25f420a0d4cfd61d3d23ec4b9c56d9f443d91377, >=96298f640104e4cd9a913a6e50b0b981829b94ff <52667c859fe33f70c2e711cb81bbd505d5eb8e75, >=96298f640104e4cd9a913a6e50b0b981829b94ff <900e4db5385ec2cacd372345a80ab9c8e105b3a3, >=96298f640104e4cd9a913a6e50b0b981829b94ff <9760b83cfd24b38caee663f429011a0dd6064fa9, >=96298f640104e4cd9a913a6e50b0b981829b94ff <9a21a631ee034b1573dce14b572a24943dbfd7ae, >=96298f640104e4cd9a913a6e50b0b981829b94ff <de37e2655b7abc3f59254c6b72256840f39fc6d5, >=96298f640104e4cd9a913a6e50b0b981829b94ff <e7aab23b7df89a3d754a5f0a7d2237548b328bd0, =4ad03ff6f680681c5f78254e37c4c856fa953629, =799263eb37a4f7f6d39334046929c3bc92452a7f, =8828622fb9b4201eeb0870587052e3d834cfaf61, =b432ea85ab8472763870dd0f2c186130dd36d68c, =b7d0ca715c1008acd2fc018f02a56fed88f78b75 | 4.20, 4.5, 4.10, 5.15.203, 6.1.168, 5.5, 5.10.253, 6.18.21, 6.19.11, 6.6.131, 6.12.80, 4.15, 042e2cd4bb11e5313b19b87593616524949e4c52, 25f420a0d4cfd61d3d23ec4b9c56d9f443d91377, 52667c859fe33f70c2e711cb81bbd505d5eb8e75, 900e4db5385ec2cacd372345a80ab9c8e105b3a3, 9760b83cfd24b38caee663f429011a0dd6064fa9, 9a21a631ee034b1573dce14b572a24943dbfd7ae, de37e2655b7abc3f59254c6b72256840f39fc6d5, e7aab23b7df89a3d754a5f0a7d2237548b328bd0 |
| linux-kernel: Kernel | >=4.14.200 <4.15, >=4.19.149 <4.20, >=4.4.238 <4.5, >=4.9.238 <4.10, >=5.11.0 <5.15.203, >=5.16.0 <6.1.168, >=5.4.69 <5.5, >=5.7.0 <5.10.253, >=6.13.0 <6.18.21, >=6.19.0 <6.19.11, >=6.2.0 <6.6.131, >=6.7.0 <6.12.80 | 4.15, 4.20, 4.5, 4.10, 5.15.203, 6.1.168, 5.5, 5.10.253, 6.18.21, 6.19.11, 6.6.131, 6.12.80 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket