CVE-2026-90088
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop
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().
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | e7c0aa45ae6c5a338661b23812bfcdef50bf3e96 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | cbc2962da99b6b89345267d3aa74b4b573340548 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 9b2e5f1928c99224345a9ed8c5dae5fc74964d6d | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | fc4851ff8dfb505e9a19efcc286712132bbd178d | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | f561e44261344adadf9d6a6dff31e3af9776d5c6 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | aeee917a4878af95f0c63e18c5f22eaf6299c7b8 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 3988cbb1be501dbff909a2ee024670e3c955a66d | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 44c98fd082eafd49d55a8a4077ff488175b2fe24 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 2.6.12 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 2.6.12 | Unavailable | None listed |
| 5.10.270 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.221 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.1.188 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.157 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.110 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.52 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.2.6 | unaffected | semver | Unavailable | 7.2.* | None listed |
| 7.3 | unaffected | original_commit_for_fix | Unavailable | * | None listed |