CVE-2026-98291: Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btintelpcie: fix off-by-one bounds check in RX submit
btintelpciesubmitrx() used frbdindex > rxq->count to guard the FRBD array access, allowing frbdindex == rxq->count to pass through and index one element past the end of the array. Change the check to = rxq->count so every out-of-range index is rejected.
This issue was reported by Claude Mythos.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems running the Linux kernel with the btintel_pcie Bluetooth driver are relevant. The issue is in the driver's RX submission path and concerns an out-of-bounds FRBD array access when the index equals the receive-queue count.
What condition triggers the out-of-bounds access?
The access can occur when frbd_index is exactly equal to rxq->count. The previous check rejected only values greater than the count, allowing this one-past-the-end index to proceed.
How can I determine whether the fix is present?
Check whether btintel_pcie_submit_rx() rejects frbd_index values greater than or equal to rxq->count. A fixed version uses a >= rxq->count bounds check rather than > rxq->count.
What can be done if updating is not immediately possible?
The provided information does not describe a configuration workaround. Prioritize applying a kernel update that includes the corrected bounds check.