CVE-2026-99009— Linux 蓝牙 RFCOMM 竞态条件漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已被修复： 蓝牙：RFCOMM：在不持有 rfcomm_mutex 的情况下连接会话套接字 当 BR/EDR 链路正在进行身份验证时，若此时发起 RFCOMM 的 connect() 调用，lockdep 会报告存在循环依赖。该报告的循环确实反映了 rfcomm_mutex 与 hdev->lock 之间的真实 AB/BA 死锁顺序。 rfcomm_security_cfm() 函数从 HCI 事件路径中被调用，而该路径已经持有 hdev->lock： 而来自用户空间的 RFCOMM
可能的 ATT&CK 技术 1 AI
T1190 · Exploit Public-Facing Application影响版本矩阵 15
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 82425b14f0fb22e46cfddc56d6465570f5ed0ce6< 4dc3d5a004b8fd59f3c905631dbb18cb601b1b41 |
affected |
1b7841ffad08e911e8c4b9470f3fa08423568940< d2206e8c78be69d21d4f5343c3e99fbaeef41cbb |
affected | ||
946d76db77ee5f922968ce558629ae47b381e3fc< cc7732b8549ecb6f02457edeb8db1f6d255e381c |
affected | ||
fbf7961964a6e93360179f64712320ae9a1e9577< f492de11b325446b0b11bc2eb86e1f546eaa61b6 |
affected | ||
759c185d0bbdb131357408f50b8735e04ed3caff< ac022970e9fb0a5f7e7d1f6c8e104c1ed924dd1c |
affected | ||
62ce8b33eb238cf18c15207332fbdc26d858f592 |
affected | ||
3873f3449701b3dc98cba577923be6493598e7a1 |
affected | ||
7ded3264106418c6456ccceaafd9fda596ce12c3 |
affected | ||
| … +7 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-99009 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex
An RFCOMM connect() issued while a BR/EDR link is being authenticated
makes lockdep report a circular dependency, and the reported cycle is a
real AB/BA between rfcomm_mutex and hdev->lock.
rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev->lock:
hci_rx_work()
hci_event_packet()
hci_cc_read_enc_key_size() [hdev->lock]
hci_encrypt_cfm() [hci_cb_list_lock]
rfcomm_security_cfm() [rfcomm_mutex]
while an RFCOMM connect() from userspace takes the same two locks the
other way round:
rfcomm_sock_connect()
rfcomm_dlc_open() [rfcomm_mutex]
__rfcomm_dlc_open()
rfcomm_session_create()
kernel_connect()
l2cap_sock_connect()
l2cap_chan_connect() [hdev->lock]
WARNING: possible circular locking dependency detected
kworker/u131:1/1128 is trying to acquire lock:
rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]
but task is already holding lock:
hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0
Chain exists of:
rfcomm_mutex --> &hdev->lock --> hci_cb_list_lock
hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.
Both orders have to be seen in the same boot, which is why a BR/EDR
connection alone is not enough to show it: a session set up by the
remote side is created by rfcomm_accept_connection() in krfcommd, which
calls kernel_accept() and never takes hdev->lock under rfcomm_mutex.
Connecting a device that authenticates and encrypts the link and then
calling connect() on an RFCOMM socket towards any address - the connect
does not have to succeed, the order is recorded before the page timeout
- reports it every time.
Only the session socket has to be connected with the lock held, and it
does not: nothing else can see the socket before it is put on the
session list. So connect it first and take rfcomm_mutex afterwards,
which removes the rfcomm_mutex -> hdev->lock order for good, rather
than keeping the HCI event path out of rfcomm_mutex.
rfcomm_session_create() becomes rfcomm_session_connect(), which returns
the connected socket without touching the session list, and
rfcomm_dlc_open() adds the session once it holds the lock again. If
another opener added a session for the same pair while this socket was
connecting, that session is used and this socket is dropped.
__rfcomm_dlc_open() now takes the session it should use, and its state
check runs after the lock is re-acquired, so a DLC that was opened or
closed in the meantime is still handled.
Over an existing ACL link the connection can complete before the
session reaches the list, and the wakeup from the socket callback is
then lost, so krfcommd is woken once the session is visible.
Connecting without the lock opens a window in which the socket can be
closed. The DLC is not on a session yet, so rfcomm_dlc_close() finds
nothing to do and returns without touching it, and rfcomm_dlc_open()
would then attach a DLC whose owner is gone. rfcomm_dlc_close() now
marks such a DLC with RFCOMM_CLOSED, and rfcomm_dlc_open() checks the
mark once it holds rfcomm_mutex again and drops the socket instead of
attaching the DLC. The mark is cleared when an open starts, so a DLC
that is reused is not affected. This covers both callers of
rfcomm_dlc_open(), the socket and the tty layer.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-99009 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-99009 的情报信息
请登录查看更多情报信息。
CVE-2026-99009 补丁与修复 (5)
同批安全公告 · Linux · 2026-10-23 · 共 217 条
| CVE-2026-98959 | 9.8 CRITICAL | btrfs 扩展属性替换处理远程代码执行漏洞 |
| CVE-2026-99078 | 9.8 CRITICAL | Mellanox mlx5e MPWQE重试时XSK缓冲区释放漏洞 |
| CVE-2026-99079 | 9.8 CRITICAL | Mellanox mlx5e 驱动 XSK 缓冲区释放漏洞 |
| CVE-2026-98988 | 8.8 HIGH | Linux 5.13 命名空间越界漏洞 |
| CVE-2026-99083 | 8.8 HIGH | ksmbd 的 krb5_authenticate() 函数堆越界写漏洞 |
| CVE-2026-99082 | 8.8 HIGH | KVM x86 内存管理漏洞 |
| CVE-2026-98870 | 8.8 HIGH | ksmbd 会话清理时存在通道移除逻辑漏洞 |
| CVE-2026-98980 | 8.8 HIGH | namei 遍历中过度挂载条目信息泄露漏洞 |
| CVE-2026-98981 | 8.8 HIGH | Linux 内核命名空间 dentry 解挂载前未哈希漏洞 |
| CVE-2026-99042 | 8.4 HIGH | io_uring 24 字节 sockaddr_in6 过滤字段填充漏洞 |
| CVE-2026-98978 | 8.4 HIGH | Linux 命名空间 锁定挂载永不失效漏洞 |
| CVE-2026-99064 | 8.1 HIGH | CIPSO 缓存选项偏移调整漏洞 |
| CVE-2026-98968 | 8.1 HIGH | AMT 中继通用查询远程代码执行漏洞 |
| CVE-2026-98993 | 7.8 HIGH | Linux 内核命名空间 clone_mnt 挂载点继承漏洞 |
| CVE-2026-99053 | 7.8 HIGH | Linux TIPC 节点引用漏洞 |
| CVE-2026-99054 | 7.8 HIGH | Linux TIPC 拓扑服务队列资源泄漏漏洞 |
| CVE-2026-99056 | 7.8 HIGH | strparser 解析器关闭时竞态条件漏洞 |
| CVE-2026-99002 | 7.8 HIGH | vmwgfx 驱动用户空间 pitch 参数验证漏洞 |
| CVE-2026-98899 | 7.8 HIGH | Linux netfilter ipset 竞态条件漏洞 |
| CVE-2026-99014 | 7.8 HIGH | Linux 蓝牙 hci_sync 命令 skb 生命周期漏洞 |
显示前 20 条，共 217 条。 查看全部 → →