All reports
Medium

kernel: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-90088

Probability of exploitation in the next 30 days: 0.22%

FIRST EPSS · 2026-11-17

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop rfcomm_apply_pn() accepts the MTU value from a remote PN (Parameter Negotiation) frame without checking for zero. When the remote peer sends an MTU of zero, d->mtu is set to 0. This causes the sendmsg path to enter an infinite loop when fragmenting data, as each fragment has size == min_t(size_t, len, 0) == 0, so the remaining length never decreases. The infinite allocation of zero-length skbs exhausts all system memory. Fix by clamping d->mtu to RFCOMM_DEFAULT_MTU when the negotiated value is zero, consistent with the initial value assigned in rfcomm_dlc_alloc().

A flaw was found in the Linux kernel's Bluetooth RFCOMM (Radio Frequency Communication) component. A remote attacker can exploit this by sending a specially crafted Parameter Negotiation (PN) frame with a zero Maximum Transmission Unit (MTU) value. This can lead to an infinite loop during data fragmentation, causing an unbounded allocation of memory and ultimately exhausting all system memory, resulting in a denial of service.