CVE-2026-31498
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-835
- Record status
- Analyzed
Affected
- Linux Kernel < 4.5
- Linux Kernel < 4.10
- Linux Kernel < 4.15
- Linux Kernel < 4.20
- Linux Kernel < 5.5
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.168
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31498.md and follow it. Check whether this project is affected by CVE-2026-31498. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
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