From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98458: Bluetooth: ISO: release unused CIS holds after channel attach
Date: Sun, 18 Oct 2026 17:15:22 +0200 [thread overview]
Message-ID: <2026101810-CVE-2026-98458-ea41@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: ISO: release unused CIS holds after channel attach
hci_bind_cis() and hci_connect_cis() return one hci_conn hold for the
ISO layer. A new channel association consumes that hold, which is
eventually released by iso_conn_free().
There are two cases where iso_chan_add() does not create an association:
it returns success when the socket is already attached to the same
iso_conn, and it returns -EBUSY when another socket is attached. The
hold returned for the current call is unused in both cases. This occurs
when deferred setup calls iso_connect_cis() again for its existing
socket, or when another socket attempts to reuse the CIS.
Detect the idempotent case while the connection is locked and release
the unused hold after iso_chan_add(). Also release it on -EBUSY. Do not
drop it for other errors: a newly allocated iso_conn releases the
transferred hold when its last temporary reference is put.
The Linux kernel CVE team has assigned CVE-2026-98458 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 69997d50ec574be816b4ee8f9cee52ebbd53f8bd and fixed in 6.12.113 with commit e0e8b70207eaf27aee0a05ec5bf2d1b6bcb004d1
Issue introduced in 6.6 with commit 69997d50ec574be816b4ee8f9cee52ebbd53f8bd and fixed in 6.18.55 with commit ed4c026cc4094dfb7a329b9d8df0ddd0be1b2458
Issue introduced in 6.6 with commit 69997d50ec574be816b4ee8f9cee52ebbd53f8bd and fixed in 7.2.9 with commit e5fcca51177f224604e3a8c926ffd5edbeb58b09
Issue introduced in 6.6 with commit 69997d50ec574be816b4ee8f9cee52ebbd53f8bd and fixed in 7.3-rc5 with commit 0fcd4dad555c96e0bd3a1b8c569f989be85c7341
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-98458
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:
net/bluetooth/iso.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/e0e8b70207eaf27aee0a05ec5bf2d1b6bcb004d1
https://git.kernel.org/stable/c/ed4c026cc4094dfb7a329b9d8df0ddd0be1b2458
https://git.kernel.org/stable/c/e5fcca51177f224604e3a8c926ffd5edbeb58b09
https://git.kernel.org/stable/c/0fcd4dad555c96e0bd3a1b8c569f989be85c7341
reply other threads:[~2026-10-18 15:18 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=2026101810-CVE-2026-98458-ea41@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.