---
title: "CVE-2026-89569: Linux Kernel Bluetooth RFCOMM - Use After Free"
description: "Linux kernel Bluetooth RFCOMM contains a use-after-free vulnerability caused by unsynchronized access to session and DLC lists in rfcomm_security_cfm(), letting local attackers cause memory corruption, exploit requires concurrent session teardown."
url: https://panop.io/threat-heartbeat/CVE-2026-89569/
---

# CVE-2026-89569 Linux Kernel Bluetooth RFCOMM - Use After Free

Linux kernel Bluetooth RFCOMM contains a use-after-free vulnerability caused by unsynchronized access to session and DLC lists in rfcomm\_security\_cfm(), letting local attackers cause memory corruption, exploit requires concurrent session teardown.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.34% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89569)

## Details

Type

Use After Free

Impact

Denial Of Service, Remote Code Execution

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for this vulnerability.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89569](https://nvd.nist.gov/vuln/detail/CVE-2026-89569)
- [https://git.kernel.org/stable/c/3873f3449701b3dc98cba577923be6493598e7a1](https://git.kernel.org/stable/c/3873f3449701b3dc98cba577923be6493598e7a1)
- [https://git.kernel.org/stable/c/62ce8b33eb238cf18c15207332fbdc26d858f592](https://git.kernel.org/stable/c/62ce8b33eb238cf18c15207332fbdc26d858f592)
- [https://git.kernel.org/stable/c/7ded3264106418c6456ccceaafd9fda596ce12c3](https://git.kernel.org/stable/c/7ded3264106418c6456ccceaafd9fda596ce12c3)
- [https://git.kernel.org/stable/c/82425b14f0fb22e46cfddc56d6465570f5ed0ce6](https://git.kernel.org/stable/c/82425b14f0fb22e46cfddc56d6465570f5ed0ce6)
- [https://git.kernel.org/stable/c/1b7841ffad08e911e8c4b9470f3fa08423568940](https://git.kernel.org/stable/c/1b7841ffad08e911e8c4b9470f3fa08423568940)
- [https://git.kernel.org/stable/c/759c185d0bbdb131357408f50b8735e04ed3caff](https://git.kernel.org/stable/c/759c185d0bbdb131357408f50b8735e04ed3caff)
- [https://git.kernel.org/stable/c/946d76db77ee5f922968ce558629ae47b381e3fc](https://git.kernel.org/stable/c/946d76db77ee5f922968ce558629ae47b381e3fc)
- [https://git.kernel.org/stable/c/fbf7961964a6e93360179f64712320ae9a1e9577](https://git.kernel.org/stable/c/fbf7961964a6e93360179f64712320ae9a1e9577)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
