From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80759: Bluetooth: hci_aml: validate firmware segment lengths
Date: Fri, 4 Sep 2026 17:10:58 +0200 [thread overview]
Message-ID: <2026090459-CVE-2026-80759-2dfb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_aml: validate firmware segment lengths
aml_download_firmware() reads two lengths from the firmware header and
uses them to build pointers before checking that the header and segment
data are present. A truncated or inconsistent firmware image can make
the driver read past firmware->data while constructing TCI commands.
Reject images shorter than the header and ensure that the ICCM and DCCM
ranges fit within the loaded firmware before downloading either segment.
The Linux kernel CVE team has assigned CVE-2026-80759 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 37bac77e4649e8158698a60addc22ec4faf5649a and fixed in 6.12.106 with commit 7733b01ed13685773ccda91035a46f87d4cfef7c
Issue introduced in 6.12 with commit 37bac77e4649e8158698a60addc22ec4faf5649a and fixed in 6.18.47 with commit e1534d49a7b8ba728e84b020f6d802aa1cb759d9
Issue introduced in 6.12 with commit 37bac77e4649e8158698a60addc22ec4faf5649a and fixed in 7.1.11 with commit 6c70253462902d835e843b470f74aa816d60af80
Issue introduced in 6.12 with commit 37bac77e4649e8158698a60addc22ec4faf5649a and fixed in 7.2.1 with commit 2763b8bcb504e30ec955474f51b99ce42fc62f3b
Issue introduced in 6.12 with commit 37bac77e4649e8158698a60addc22ec4faf5649a and fixed in 7.3-rc1 with commit 2bf6b9baca9372ea51b6d0f2820dc9bf29a83ef4
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-80759
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/hci_aml.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/7733b01ed13685773ccda91035a46f87d4cfef7c
https://git.kernel.org/stable/c/e1534d49a7b8ba728e84b020f6d802aa1cb759d9
https://git.kernel.org/stable/c/6c70253462902d835e843b470f74aa816d60af80
https://git.kernel.org/stable/c/2763b8bcb504e30ec955474f51b99ce42fc62f3b
https://git.kernel.org/stable/c/2bf6b9baca9372ea51b6d0f2820dc9bf29a83ef4
reply other threads:[~2026-09-04 15:13 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=2026090459-CVE-2026-80759-2dfb@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.