CVE-2026-99010

Bluetooth: RFCOMM: free the skb when the DLC has no owner

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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.371% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 05145638e0db770267c39615c8ce51ab058e34cf (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 91492e9194f3b10bc1eb50683ac440b74a487e39 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding a835b7f445427c7bdfc7169a97e0a1bec375e408 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding a54ce160e3ef7e50ec94e0ac4131c3d0f9f739b9 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding c3f76b025cbbb0ab47310dbe7de18092d89f2a99 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 4f46de658ce61968aef5ea7ae809d1c180330544 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding b8814161b14c610b7a09527433301d8ad8180aef (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 9d1afbf60ed53c5b051cd124153e0ae3078c8b93 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.12 (affected)
  • 0 up to but excluding 2.6.12 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References