]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type
authorLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
Wed, 9 Jul 2025 19:02:56 +0000 (15:02 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 24 Jul 2025 06:58:28 +0000 (08:58 +0200)
commit47108424e090deb7261a9c12bec7bf481a8a24c6
tree6064204bdf2dc9ff349c06deb6e45b8626fb0657
parent0d380dd26028a75c9e880453214651f64890a30a
Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type

commit 6ec3185fbc3528f2284c347fb9bd8be6fa672ed4 upstream.

Due to what seem to be a bug with variant version returned by some
firmwares the code may set hdev->classify_pkt_type with
btintel_classify_pkt_type when in fact the controller doesn't even
support ISO channels feature but may use the handle range expected from
a controllers that does causing the packets to be reclassified as ISO
causing several bugs.

To fix the above btintel_classify_pkt_type will attempt to check if the
controller really supports ISO channels and in case it doesn't don't
reclassify even if the handle range is considered to be ISO, this is
considered safer than trying to fix the specific controller/firmware
version as that could change over time and causing similar problems in
the future.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=219553
Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565
Link: https://github.com/StarLabsLtd/firmware/issues/180
Fixes: f25b7fd36cc3 ("Bluetooth: Add vendor-specific packet classification for ISO data")
Cc: stable@vger.kernel.org
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Tested-by: Sean Rhodes <sean@starlabs.systems>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/bluetooth/btintel.c