VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

CVE-2026-99010: Linux kernel · Bluetooth: RFCOMM: free the skb when the DLC has no owner

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99010· Medium

Not known to be exploited.

Data as of 28 Oct 2026, 01:58 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-9.9 6 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is applied, monitoring for unusual memory usage related to Bluetooth RFCOMM and limiting exposure to untrusted Bluetooth devices may reduce risk.

Description

A memory leak vulnerability exists in the Linux kernel's Bluetooth RFCOMM implementation due to failure to free socket buffers (skb) when a Data Link Connection (DLC) has no owner. This leak occurs because the socket implementation does not free the skb in certain states, causing continuous memory consumption as data frames are received. The issue affects specific Linux kernel versions and has been publicly disclosed.

Impact

The vulnerability causes a memory leak in the Linux kernel Bluetooth RFCOMM implementation, which can lead to resource exhaustion on affected systems. This leak occurs when data frames are received on a DLC that has no owner, causing the socket buffers to be leaked continuously. While this does not directly allow code execution or privilege escalation, the growing memory consumption could degrade system stability or cause denial of service due to resource depletion.

Summary

CVE-2026-99010 describes a memory leak in the Linux kernel Bluetooth RFCOMM layer. The function rfcomm_recv_data() hands the skb to a callback without freeing it, transferring ownership. When the DLC has no owner, the tty implementation frees the skb, but the socket implementation does not, resulting in a leak. A connected DLC can have no owner during a window after rfcomm_sock_destruct() clears the owner but before the DLC is closed. Incoming data frames in this window cause skb leaks that accumulate because the remote side continues sending data due to credit management logic. The vulnerability affects multiple specific Linux kernel versions.

GCVE source: db.gcve.eu
OSV ID: UBUNTU-CVE-2026-99010
Osv Schema Version: 1.7.0
Ecosystems: Ubuntu:Pro:14.04:LTS, Ubuntu:Pro:16.04:LTS, Ubuntu:16.04:LTS, Ubuntu:Pro:FIPS-updates:16.04:LTS, Ubuntu:Pro:FIPS:16.04:LTS, Ubuntu:Pro:18.04:LTS, Ubuntu:18.04:LTS, Ubuntu:Pro:FIPS-updates:18.04:LTS, Ubuntu:Pro:FIPS:18.04:LTS, Ubuntu:Pro:20.04:LTS, Ubuntu:20.04:LTS, Ubuntu:Pro:FIPS-updates:20.04:LTS, Ubuntu:Pro:FIPS:20.04:LTS, Ubuntu:22.04:LTS, Ubuntu:Nvidia-BlueField:22.04:LTS, Ubuntu:Pro:Realtime:22.04:LTS, Ubuntu:Pro:FIPS-preview:22.04:LTS, Ubuntu:Pro:FIPS-updates:22.04:LTS, Ubuntu:24.04:LTS, Ubuntu:Nvidia-BlueField:24.04:LTS, Ubuntu:Pro:Realtime:24.04:LTS, Ubuntu:Pro:FIPS-updates:24.04:LTS, Ubuntu:26.10, Ubuntu:26.04:LTS

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 01:58 UTC

Technical details

References

Community reviews

Related threats