Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90088Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop

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

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 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)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e7c0aa45ae6c5a338661b23812bfcdef50bf3e96
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cbc2962da99b6b89345267d3aa74b4b573340548
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9b2e5f1928c99224345a9ed8c5dae5fc74964d6d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fc4851ff8dfb505e9a19efcc286712132bbd178d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f561e44261344adadf9d6a6dff31e3af9776d5c6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < aeee917a4878af95f0c63e18c5f22eaf6299c7b8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3988cbb1be501dbff909a2ee024670e3c955a66d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 44c98fd082eafd49d55a8a4077ff488175b2fe24
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90088 badge
[![CVE-2026-90088](https://cveledger.app/badge/CVE-2026-90088.svg)](https://cveledger.app/cve/CVE-2026-90088)

Record last updated .