From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74530: Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback
Date: Sat, 15 Aug 2026 21:26:51 +0900 [thread overview]
Message-ID: <2026081546-CVE-2026-74530-ee6f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback
There is theoretical UAF if the conn is freed while the hci_sync task is
running.
Hold refcount to avoid that. Handle NULL hcon, return 0 + do nothing to
match the previous behavior.
The Linux kernel CVE team has assigned CVE-2026-74530 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 024421cf39923927ab2b5fe895d1d922b9abe67f and fixed in 7.1.8 with commit 2d91e6244b69d752503b2d44020d8b0e323dbd38
Issue introduced in 6.15 with commit 024421cf39923927ab2b5fe895d1d922b9abe67f and fixed in 7.2-rc6 with commit 56e78b670356caab0b607e8aad4cf819a1909d07
Issue introduced in 6.12.28 with commit 620810ac1f7f1133a9ac403e132b3ad6995ddf39
Issue introduced in 6.14.6 with commit ee0586ad64a805eaf1a9a10100e908627a561e34
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-74530
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/hci_sync.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/2d91e6244b69d752503b2d44020d8b0e323dbd38
https://git.kernel.org/stable/c/56e78b670356caab0b607e8aad4cf819a1909d07
reply other threads:[~2026-08-15 12:31 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=2026081546-CVE-2026-74530-ee6f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox