PatchSiren cyber security CVE debrief
CVE-2026-99009 Linux CVE debrief
A vulnerability in the Linux kernel's Bluetooth RFCOMM implementation can lead to a circular dependency lock issue. An attacker may be able to exploit this issue to cause a denial of service. Linux kernel developers have addressed this issue. Users should verify their kernel versions and update if necessary. The issue arises when an RFCOMM connect() is issued while a BR/EDR link is being authenticated, potentially leading to a denial of service. This vulnerability affects Linux kernel developers and administrators responsible for maintaining Linux-based systems.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-23
- Original CVE updated
- 2026-10-30
- Advisory published
- 2026-10-23
- Advisory updated
- 2026-10-30
Who should care
Linux kernel developers and administrators responsible for maintaining Linux-based systems should assess exposure and apply updates if necessary. They should also review compensating controls for exposed systems and monitor system logs for potential exploitation attempts. Affected operators, platforms, and security teams need to be aware of the vulnerability and its potential impact.
Why it matters
The Linux kernel's Bluetooth RFCOMM implementation is vulnerable to a circular dependency lock issue, potentially leading to a denial of service. Linux kernel developers and administrators should assess exposure and apply updates if necessary.
- Denial of service due to circular dependency lock issue
- Potential disruption to Bluetooth connectivity
Technical summary
The Linux kernel's Bluetooth RFCOMM implementation is vulnerable to a circular dependency lock issue. This issue can be triggered when an RFCOMM connect() is issued while a BR/EDR link is being authenticated, potentially leading to a denial of service. The vulnerability affects Linux kernel developers and administrators responsible for maintaining Linux-based systems. The issue has been addressed by Linux kernel developers. Affected systems should be updated to prevent potential exploitation. The vulnerability is related to the Bluetooth RFCOMM implementation in the Linux kernel.
Defensive priority
Apply kernel updates to address the Bluetooth RFCOMM vulnerability
Recommended defensive actions
- Verify kernel version and apply updates if necessary
- Monitor system logs for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The CVE record and associated source item provide details on the vulnerability, including a description of the issue and affected kernel versions. The Linux kernel's Bluetooth RFCOMM implementation is vulnerable to a circular dependency lock issue. Evidence is based on CVE Program records and associated source items. Defenders should verify kernel versions and assess exposure. The vulnerability has been addressed by Linux kernel developers.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-99009 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-99009
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-99009 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-99009
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/99xxx/CVE-2026-99009.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d7a3bf6f55ab77d465206b25fe3418091c3d4b92
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/172b152119643018a2ed792e5096f33a4491c7de
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/caf78390f78a005d5cdc1db2eb467b2794bbf020
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4dc3d5a004b8fd59f3c905631dbb18cb601b1b41
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d2206e8c78be69d21d4f5343c3e99fbaeef41cbb
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/cc7732b8549ecb6f02457edeb8db1f6d255e381c
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f492de11b325446b0b11bc2eb86e1f546eaa61b6
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.