CVE-2026-90088Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e7c0aa45ae6c5a338661b23812bfcdef50bf3e96
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cbc2962da99b6b89345267d3aa74b4b573340548
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9b2e5f1928c99224345a9ed8c5dae5fc74964d6d
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fc4851ff8dfb505e9a19efcc286712132bbd178d
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f561e44261344adadf9d6a6dff31e3af9776d5c6
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < aeee917a4878af95f0c63e18c5f22eaf6299c7b8
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3988cbb1be501dbff909a2ee024670e3c955a66d
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 44c98fd082eafd49d55a8a4077ff488175b2fe24
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/e7c0aa45ae6c5a338661b23812bfcdef50bf3e96 (opens in a new tab)
- https://git.kernel.org/stable/c/cbc2962da99b6b89345267d3aa74b4b573340548 (opens in a new tab)
- https://git.kernel.org/stable/c/9b2e5f1928c99224345a9ed8c5dae5fc74964d6d (opens in a new tab)
- https://git.kernel.org/stable/c/fc4851ff8dfb505e9a19efcc286712132bbd178d (opens in a new tab)
- https://git.kernel.org/stable/c/f561e44261344adadf9d6a6dff31e3af9776d5c6 (opens in a new tab)
- https://git.kernel.org/stable/c/aeee917a4878af95f0c63e18c5f22eaf6299c7b8 (opens in a new tab)
- https://git.kernel.org/stable/c/3988cbb1be501dbff909a2ee024670e3c955a66d (opens in a new tab)
- https://git.kernel.org/stable/c/44c98fd082eafd49d55a8a4077ff488175b2fe24 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81949 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90088)Record last updated .