CVE-2026-31498
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.170-1 |
| debian | forky | fixed | 6.19.11-1 |
| debian | sid | fixed | 6.19.11-1 |
| debian | trixie | fixed | 6.12.85-1 |
| debian | bullseye | fixed | 6.1.170-1~deb11u1 |
| linux-kernel | affected | 4.5 | |
| linux-kernel | 5.7 | affected | |
| linux-kernel | 7.0 | affected | |
References
- https://git.kernel.org/stable/c/042e2cd4bb11e5313b19b87593616524949e4c52
- https://git.kernel.org/stable/c/25f420a0d4cfd61d3d23ec4b9c56d9f443d91377
- https://git.kernel.org/stable/c/52667c859fe33f70c2e711cb81bbd505d5eb8e75
- https://git.kernel.org/stable/c/900e4db5385ec2cacd372345a80ab9c8e105b3a3
- https://git.kernel.org/stable/c/9760b83cfd24b38caee663f429011a0dd6064fa9
- https://git.kernel.org/stable/c/9a21a631ee034b1573dce14b572a24943dbfd7ae
- https://git.kernel.org/stable/c/de37e2655b7abc3f59254c6b72256840f39fc6d5
- https://git.kernel.org/stable/c/e7aab23b7df89a3d754a5f0a7d2237548b328bd0
- https://www.suse.com/security/cve/CVE-2026-31498.html
- https://security-tracker.debian.org/tracker/CVE-2026-31498
CWEs
CWE-835
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.