# CVE-2026-80914: Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready

> A use-after-free in the Linux kernel Bluetooth ISO subsystem allows attackers to cause denial of service or execute arbitrary code via race conditions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99959, BELL-CVE-2026-80914, DEBIAN-CVE-2026-80914, GHSA-xmw2-vj5q-xhxr, UBUNTU-CVE-2026-80914

## What is CVE-2026-80914?

CVE-2026-80914 is a high-severity use after free vulnerability in Linux, published on 9 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready

iso_conn_ready() looks up the BIS listener socket with iso_get_sock(),
which takes a reference, and then, without re-checking its state,
creates a child socket from it:

    parent = iso_get_sock(hdev, ...);
    if (!parent)
        return;

    lock_sock(parent);
    sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);
    ...
    iso_chan_add(conn, sk, parent);
    ...
    release_sock(parent);
    sock_put(parent);

If the listener socket is closed concurrently, between iso_get_sock()
and lock_sock(), the reference taken by iso_get_sock() may be the last
one: the close path drops the link-list reference, and once
iso_conn_ready() drops its own reference at the end of the function the
socket is freed.  The child socket, however, is already linked to the
freed parent, and a later disconnect of the child runs iso_chan_del()
-> bt_accept_unlink(), which dereferences the dangling parent pointer
into the freed accept queue (a use-after-free).  The same dangling
pointer is also dereferenced through parent->***() in
iso_chan_del().

Fix it the same way the connected (non-BIS) path was fixed in commit
0d255e63fcf3 ("Bluetooth: ISO: hold sk properly in iso_conn_ready"):
after taking the socket lock, re-check that the parent is still a
listening, alive socket, and bail out otherwise.

## Which versions are affected by CVE-2026-80914?


## How do I fix CVE-2026-80914?

Apply the vendor's patch.

## Is CVE-2026-80914 being exploited?

There is no known exploitation of CVE-2026-80914 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80914 and fix it if it is affected.

What it is: CVE-2026-80914 is a high-severity use after free vulnerability in Linux, published on 9 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80914 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80914/ (Markdown: https://insights.sbomify.com/CVE-2026-80914/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80914
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80914
- OSV: https://osv.dev/vulnerability/CVE-2026-80914

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80914/
Summaries are generated and may contain mistakes; the official description above is the record.