CVE-2026-99010Bluetooth: RFCOMM: free the skb when the DLC has no owner
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% 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: free the skb when the DLC has no owner rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device: static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc, struct sk_buff *skb) { struct rfcomm_dev *dev = dlc->owner; if (!dev) { kfree_skb(skb); return; } The socket implementation returns without freeing it, and the skb is leaked. A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each. The leak does not stop on its own either. The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing. Free the skb, as the tty side does.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
- 7 days later
· 7 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.18% · top 93% of all CVEs (12 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 – < 05145638e0db770267c39615c8ce51ab058e34cf
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 91492e9194f3b10bc1eb50683ac440b74a487e39
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a835b7f445427c7bdfc7169a97e0a1bec375e408
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a54ce160e3ef7e50ec94e0ac4131c3d0f9f739b9
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c3f76b025cbbb0ab47310dbe7de18092d89f2a99
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4f46de658ce61968aef5ea7ae809d1c180330544
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b8814161b14c610b7a09527433301d8ad8180aef
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9d1afbf60ed53c5b051cd124153e0ae3078c8b93
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.11 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/05145638e0db770267c39615c8ce51ab058e34cf (opens in a new tab)
- https://git.kernel.org/stable/c/91492e9194f3b10bc1eb50683ac440b74a487e39 (opens in a new tab)
- https://git.kernel.org/stable/c/a835b7f445427c7bdfc7169a97e0a1bec375e408 (opens in a new tab)
- https://git.kernel.org/stable/c/a54ce160e3ef7e50ec94e0ac4131c3d0f9f739b9 (opens in a new tab)
- https://git.kernel.org/stable/c/c3f76b025cbbb0ab47310dbe7de18092d89f2a99 (opens in a new tab)
- https://git.kernel.org/stable/c/4f46de658ce61968aef5ea7ae809d1c180330544 (opens in a new tab)
- https://git.kernel.org/stable/c/b8814161b14c610b7a09527433301d8ad8180aef (opens in a new tab)
- https://git.kernel.org/stable/c/9d1afbf60ed53c5b051cd124153e0ae3078c8b93 (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-108804 (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-99010)Record last updated .