CVE-2026-99010: Linux
EPSS: 0.2% probability of exploitation activity in the next 30 days.
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.
What to do
The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.
- Linux, from 2.6.12, before 5.10.273: fixed in 5.10.273
- Linux, from 5.11, before 5.15.224: fixed in 5.15.224
- Linux, from 5.16, before 6.1.191: fixed in 6.1.191
- Linux, from 6.2, before 6.6.160: fixed in 6.6.160
- Linux, from 6.7, before 6.12.113: fixed in 6.12.113
- Linux, from 6.13, before 6.18.57: fixed in 6.18.57
- Linux, from 6.19, before 7.2.11: fixed in 7.2.11
Affected products
- Linux Linux: from 2.6.12, before 5.10.273 (fixed in 5.10.273); from 5.11, before 5.15.224 (fixed in 5.15.224); from 5.16, before 6.1.191 (fixed in 6.1.191); from 6.2, before 6.6.160 (fixed in 6.6.160); from 6.7, before 6.12.113 (fixed in 6.12.113); from 6.13, before 6.18.57 (fixed in 6.18.57); …
Published 2026-10-23. Last modified 2026-10-30.