{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99009 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99009 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99009 and fix it if it is affected.\n\nWhat it is: CVE-2026-99009 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99009 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99009/ (Markdown: https://insights.sbomify.com/CVE-2026-99009/index.md)","id":"CVE-2026-99009","markdown":"https://insights.sbomify.com/CVE-2026-99009/index.md","name":"CVE-2026-99009","record":{"aliases":["AZL-110855","BELL-CVE-2026-99009","DEBIAN-CVE-2026-99009","GHSA-5rpp-jh2w-vm6p","UBUNTU-CVE-2026-99009"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: connect the session socket without rfcomm_mutex\n\nAn RFCOMM connect() issued while a BR/EDR link is being authenticated\nmakes lockdep report a circular dependency, and the reported cycle is a\nreal AB/BA between rfcomm_mutex and hdev-\u003elock.\n\nrfcomm_security_cfm() is called from the HCI event path, which already\nholds hdev-\u003elock:\n\n  hci_rx_work()\n    hci_event_packet()\n      hci_cc_read_enc_key_size()   [hdev-\u003elock]\n        hci_encrypt_cfm()          [hci_cb_list_lock]\n          rfcomm_security_cfm()    [rfcomm_mutex]\n\nwhile an RFCOMM connect() from userspace takes the same two locks the\nother way round:\n\n  rfcomm_sock_connect()\n    rfcomm_dlc_open()              [rfcomm_mutex]\n      __rfcomm_dlc_open()\n        rfcomm_session_create()\n          kernel_connect()\n            l2cap_sock_connect()\n              l2cap_chan_connect() [hdev-\u003elock]\n\n  WARNING: possible circular locking dependency detected\n  kworker/u131:1/1128 is trying to acquire lock:\n  rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]\n  but task is already holding lock:\n  hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0\n  Chain exists of:\n    rfcomm_mutex --\u003e \u0026hdev-\u003elock --\u003e hci_cb_list_lock\n\nhci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback\nthe same way.\n\nBoth orders have to be seen in the same boot, which is why a BR/EDR\nconnection alone is not enough to show it: a session set up by the\nremote side is created by rfcomm_accept_connection() in krfcommd, which\ncalls kernel_accept() and never takes hdev-\u003elock under rfcomm_mutex.\nConnecting a device that authenticates and encrypts the link and then\ncalling connect() on an RFCOMM socket towards any address - the connect\ndoes not have to succeed, the order is recorded before the page timeout\n- reports it every time.\n\nOnly the session socket has to be connected with the lock held, and it\ndoes not: nothing else can see the socket before it is put on the\nsession list.  So connect it first and take rfcomm_mutex afterwards,\nwhich removes the rfcomm_mutex -\u003e hdev-\u003elock order for good, rather\nthan keeping the HCI event path out of rfcomm_mutex.\n\nrfcomm_session_create() becomes rfcomm_session_connect(), which returns\nthe connected socket without touching the session list, and\nrfcomm_dlc_open() adds the session once it holds the lock again.  If\nanother opener added a session for the same pair while this socket was\nconnecting, that session is used and this socket is dropped.\n__rfcomm_dlc_open() now takes the session it should use, and its state\ncheck runs after the lock is re-acquired, so a DLC that was opened or\nclosed in the meantime is still handled.\n\nOver an existing ACL link the connection can complete before the\nsession reaches the list, and the wakeup from the socket callback is\nthen lost, so krfcommd is woken once the session is visible.\n\nConnecting without the lock opens a window in which the socket can be\nclosed.  The DLC is not on a session yet, so rfcomm_dlc_close() finds\nnothing to do and returns without touching it, and rfcomm_dlc_open()\nwould then attach a DLC whose owner is gone.  rfcomm_dlc_close() now\nmarks such a DLC with RFCOMM_CLOSED, and rfcomm_dlc_open() checks the\nmark once it holds rfcomm_mutex again and drops the socket instead of\nattaching the DLC.  The mark is cleared when an open starts, so a DLC\nthat is reused is not affected.  This covers both callers of\nrfcomm_dlc_open(), the socket and the tty layer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex","id":"CVE-2026-99009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Bluetooth: RFCOMM: free the skb when the DLC has no owner","id":"CVE-2026-99010"},"packages":[],"prev":{"headline":"Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown","id":"CVE-2026-99008"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99009/"}