# CVE-2025-40141: Bluetooth: ISO: Fix possible UAF on iso_conn_free

> A use-after-free vulnerability in the Linux kernel's Bluetooth ISO subsystem allows attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-40141, DEBIAN-CVE-2025-40141, GHSA-rr62-6cpm-ww8h, ROOT-OS-DEBIAN-13-CVE-2025-40141, ROOT-OS-UBUNTU-2404-CVE-2025-40141, UBUNTU-CVE-2025-40141

## What is CVE-2025-40141?

CVE-2025-40141 is a high-severity use after free vulnerability in Linux, published on 12 Nov 2025. 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 possible UAF on iso_conn_free

This attempt to fix similar issue to sco_conn_free where if the
conn->sk is not set to NULL may lead to UAF on iso_conn_free.

## Which versions are affected by CVE-2025-40141?


## How do I fix CVE-2025-40141?

Apply the vendor's patch.

## Is CVE-2025-40141 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40141 and fix it if it is affected.

What it is: CVE-2025-40141 is a high-severity use after free vulnerability in Linux, published on 12 Nov 2025. 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-2025-40141 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-2025-40141/ (Markdown: https://insights.sbomify.com/CVE-2025-40141/index.md)
```

## Sources

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

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