VulnerabilityPublished 26 Oct 2026Updated 28 Oct 2026

CVE-2026-99094: Linux kernel · Bluetooth: btintel_pcie: fix TX descriptor bounds check

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99094

Not known to be exploited.

Data as of 29 Oct 2026, 00:58 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 26 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

A fix is available that corrects the bounds check in the btintel_pcie_prepare_tx() function. Users should apply the updated Linux kernel versions that include this patch. Specific affected versions are listed and should be upgraded to patched releases. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel Bluetooth driver btintel_pcie was fixed to correct a bounds check error in the TX descriptor handling. The function btintel_pcie_prepare_tx() improperly used an index that could exceed array bounds, potentially leading to out-of-bounds access. This issue affects multiple specific Linux kernel versions used in various Ubuntu releases.

Impact

The vulnerability could lead to out-of-bounds memory access in the Bluetooth driver, which may cause system instability or crashes. No known exploits in the wild have been reported. The impact is considered medium severity based on the potential for memory corruption but no confirmed exploitation.

Summary

The Linux kernel Bluetooth driver component btintel_pcie had a flaw in the function btintel_pcie_prepare_tx() where the tfd_index was used to access transmit frame descriptor (TFD) and data buffer arrays before the index was advanced modulo txq->count. This allowed an index equal to txq->count, which is one past the end of the arrays, to pass the bounds check. The vulnerability was resolved by rejecting such out-of-bounds indices, preventing potential memory corruption or instability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 00:58 UTC

Technical details

References

Community reviews

Related threats