From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98291: Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit
Date: Tue, 6 Oct 2026 10:46:32 +0200 [thread overview]
Message-ID: <2026100607-CVE-2026-98291-1b4e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit
btintel_pcie_submit_rx() used frbd_index > rxq->count to guard the
FRBD array access, allowing frbd_index == 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.
The Linux kernel CVE team has assigned CVE-2026-98291 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit c2b636b3f788d10486a6691ad6dd3ec4c93bd78e and fixed in 6.12.112 with commit b5214d72bfdf8ef7744d0c8147e6ebb09b36b259
Issue introduced in 6.10 with commit c2b636b3f788d10486a6691ad6dd3ec4c93bd78e and fixed in 6.18.54 with commit 18464860ce27af0dccd2fc72830610b85b518cff
Issue introduced in 6.10 with commit c2b636b3f788d10486a6691ad6dd3ec4c93bd78e and fixed in 7.2.8 with commit de4c3c72bcc6e8474f70c22427f94ca44bccd890
Issue introduced in 6.10 with commit c2b636b3f788d10486a6691ad6dd3ec4c93bd78e and fixed in 7.3-rc4 with commit 2ea5a87a5a7ae58cb2662b8a7d06f209383e1765
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98291
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/bluetooth/btintel_pcie.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b5214d72bfdf8ef7744d0c8147e6ebb09b36b259
https://git.kernel.org/stable/c/18464860ce27af0dccd2fc72830610b85b518cff
https://git.kernel.org/stable/c/de4c3c72bcc6e8474f70c22427f94ca44bccd890
https://git.kernel.org/stable/c/2ea5a87a5a7ae58cb2662b8a7d06f209383e1765
reply other threads:[~2026-10-06 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026100607-CVE-2026-98291-1b4e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.