[CVE-2026-80721][MODERATE 7.0] Bluetooth: ISO: ensure no dangling hcon references in iso_conn [ Upstream

[CVE-2026-80721][MODERATE 7.0] Bluetooth: ISO: ensure no dangling hcon references in iso_conn [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80721
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: Bluetooth: ISO: ensure no dangling hcon references in iso_conn [ Upstream
Commit: e941799c31f68e67ce0976efb38a79101f921b64
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e941799c31f68e67ce0976efb38a79101f921b64
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80721
Analysis date: Fri, 28 Aug 2026 05:42:31 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80721 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80721

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-80721	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;*CWE-664;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.5';DESCR 'Bluetooth ISO sockets could keep a dangling hcon reference after iso_conn_del, allowing later socket side code to dereference an hci_conn that should no longer be used. The bug is a lifetime and race issue between ISO connection teardown and socket access, and can plausibly result in a stale pointer dereference or use-after-free style condition. For the CVSS the PR:N value is used for the paranoid score because an adjacent Bluetooth peer may influence connection teardown without having an account on the victim system, although reliable triggering depends on Bluetooth ISO support and connection state. The issue is not Internet reachable, but it is adjacent network reachable over Bluetooth radio range. Impact is at least denial of service via kernel crash, and in the paranoid interpretation may include confidentiality or integrity impact if the stale hcon reference is reachable after reuse of freed memory.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE RACE NETWORK  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=4

1. ActionableScore
* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

2. Signal breakdown
* Remote reachable / network-triggerable: +2. Bluetooth ISO is not Internet reachable, but an adjacent Bluetooth peer can influence connection setup and teardown paths.
* Memory corruption, weak/indirect corruption candidate: +1. The patch addresses a dangling `hcon` reference, but does not show attacker-controlled reclaim, overwrite, callback control, or type confusion.
* Real lifetime corruption: +1. The issue is explicitly about stale lifetime handling between `iso_conn`, `hci_conn`, and socket-side access.
* Reliable kernel crash / strong DoS: +1. A stale `hcon` dereference can plausibly crash the kernel or Bluetooth stack.
* Hard or unreliable race / special timing required: -1. The commit specifically mentions race reasoning around who holds the last reference.
* Rare AND difficult-to-reach subsystem/configuration: -1 conservative only. Bluetooth ISO requires Bluetooth support, ISO-capable hardware, and a relevant connection state.
* Paranoid delta: +1 by not applying the rare-subsystem penalty, because Bluetooth is a real adjacent attack surface and the bug is a dangling kernel object reference.

3. Reachability analysis
An adjacent Bluetooth peer may trigger the affected path by influencing ISO connection establishment or teardown, especially around connect or disconnect confirmation handling. No local account is required for the paranoid interpretation, so PR:N is defensible in CVSS terms for adjacent-network exposure. Reliable triggering likely depends on Bluetooth being enabled, ISO support being present, and specific connection state timing. Containers and namespaces do not meaningfully improve reachability unless they expose Bluetooth management or socket access, but the adjacent peer model is more relevant here than a local namespace model.

4. Severity interpretation
This is not an ordinary Low issue because the patch fixes a dangling pointer / lifetime race in kernel Bluetooth connection state. It is also not a strong Important candidate on the provided evidence, because there is no demonstrated reclaim primitive, write-after-free, type confusion, callback dispatch, or controlled object replacement. Realistic impact is most strongly supported as adjacent-network DoS. Theoretical memory corruption risk exists because stale `hcon` references can become UAF-like, but the patch context supports weak corruption concern rather than proven LPE.

5. One-sentence report phrase
Bluetooth ISO connection teardown could leave sockets with a dangling `hcon` reference after `iso_conn_del()`, allowing an adjacent Bluetooth peer under specific ISO connection timing conditions to trigger a stale pointer dereference or UAF-like crash, with realistic impact as DoS and manual review warranted for memory lifetime risk.

6. Manual review recommendation
MANUAL CHECK REQUIRED. YES REQUIRES MANUAL CHECK.
Reason: adjacent-network reachable lifetime/race bug with dangling kernel object reference, capped below strong Important without evidence of reclaim or overwrite, but still too security-relevant to auto-close.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: Bluetooth: ISO: ensure no dangling hcon references in iso_conn [ Upstream
Commit: e941799c31f68e67ce0976efb38a79101f921b64
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e941799c31f68e67ce0976efb38a79101f921b64

Changed files:
  net/bluetooth/iso.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e941799c31f68e67ce0976efb38a79101f921b64

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80721 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80721

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).