CVE-2026-80819— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于蓝牙RFCOMM在调用rfcomm_dlc_accept()时未持有rfcomm_mutex锁，可能因远程DISC导致空指针取消引用，引发内核崩溃。
可能的 ATT&CK 技术 1 AI
T1598 · Phishing for Information影响版本矩阵 20
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | bb23c0ab824653be4aa7dfca15b07b3059717004< d8d686dd5662a7c4745e4515f1237a9f3b7df181 |
affected |
bb23c0ab824653be4aa7dfca15b07b3059717004< eb71d5a1ea8ff2683e394b48ae3cd676037ab4c2 |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< 56f0aa75c7640e46397ef73bea251fcbef9150c0 |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< 362726c9c6e56eea4262109183e49868c39ccd3a |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< 825b95561d7b7c393df9e7bc295451aaeadc3d18 |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< d4b1a13b1eff2e80925c7368ffdeaaa50cba93df |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< 355bfd57ca4ca881c6eb03ca813b440a094b1f44 |
affected | ||
bb23c0ab824653be4aa7dfca15b07b3059717004< b405c2f96ae2e37375105881890f7738833b1d62 |
affected | ||
| … +12 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-80819 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept
rfcomm_sock_recvmsg() completes a deferred setup by calling
rfcomm_dlc_accept() without holding any RFCOMM lock:
if (test_and_clear_bit(RFCOMM_DEFER_SETUP, &d->flags)) {
rfcomm_dlc_accept(d);
return 0;
}
and rfcomm_dlc_accept() dereferences the session on its first line:
struct sock *sk = d->session->sock->sk;
Every other path that touches d->session runs under rfcomm_mutex:
rfcomm_dlc_open(), rfcomm_dlc_close(), rfcomm_dlc_exists(),
rfcomm_dlc_send_rpn(), and the RFCOMM thread through
rfcomm_process_sessions(). rfcomm_connect_ind() is even documented as
"called under rfcomm_lock()". This call site is the only one that skips
it.
The RFCOMM_DEFER_SETUP bit looks like it serialises the accept against
teardown, since __rfcomm_dlc_close() returns early when it wins the
test_and_clear. But rfcomm_recv_disc() forces the state first:
d->state = BT_CLOSED;
__rfcomm_dlc_close(d, err);
and the early return only covers BT_CONNECT, BT_CONFIG, BT_OPEN and
BT_CONNECT2. With the state already BT_CLOSED that switch does not
match, the bit is never consulted, and __rfcomm_dlc_close() falls
through to rfcomm_dlc_unlink(), which sets d->session = NULL.
So a remote DISC on a deferred dlc clears the session while leaving
RFCOMM_DEFER_SETUP set. The next recvmsg() then passes the
test_and_clear and dereferences a NULL session. No timing window is
needed: once the DISC has been processed, the dereference is
unconditional.
Give rfcomm_dlc_accept() the same shape as rfcomm_dlc_open() and
rfcomm_dlc_close(): an exported wrapper that takes rfcomm_mutex and
re-checks the session, around a __rfcomm_dlc_accept() that the two
in-core callers, which already hold the mutex, keep using.
Reproduced on a KASAN + PROVE_LOCKING kernel with a BR/EDR peer emulated
over /dev/vhci: the peer brings up an ACL link, opens L2CAP on the
RFCOMM PSM, starts a session, opens a dlc on a channel bound with
BT_DEFER_SETUP, and sends DISC after the socket is accepted. recv() on
the accepted socket then hits:
Oops: general protection fault
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
RIP: 0010:rfcomm_dlc_accept+0x54/0x350
Call Trace:
rfcomm_sock_recvmsg+0x1cd/0x230
sock_recvmsg+0x166/0x1c0
__sys_recvfrom+0x20d/0x300
0x10 is the offset of sock in struct rfcomm_session. With this patch the
same run completes with recv() returning 0 and no report, and lockdep
stays quiet, confirming rfcomm_mutex is still taken before lock_sock on
this path as it is on the thread side.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于蓝牙RFCOMM在调用rfcomm_dlc_accept()时未持有rfcomm_mutex锁，可能因远程DISC导致空指针取消引用，引发内核崩溃。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-80819 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-80819 的情报信息
请登录查看更多情报信息。
CVE-2026-80819 补丁与修复 (8)
CVE-2026-80819 厂商页面 (1)
同批安全公告 · Linux · 2026-09-04 · 共 156 条
| CVE-2026-80865 | Linux kernel 安全漏洞 | |
| CVE-2026-80856 | Linux kernel 安全漏洞 | |
| CVE-2026-80857 | Linux kernel 安全漏洞 | |
| CVE-2026-80858 | Linux kernel 安全漏洞 | |
| CVE-2026-80859 | Linux kernel 安全漏洞 | |
| CVE-2026-80860 | Linux kernel 安全漏洞 | |
| CVE-2026-80861 | Linux kernel 安全漏洞 | |
| CVE-2026-80862 | Linux kernel 安全漏洞 | |
| CVE-2026-80863 | Linux kernel 安全漏洞 | |
| CVE-2026-80864 | Linux kernel 安全漏洞 | |
| CVE-2026-80870 | Linux kernel 安全漏洞 | |
| CVE-2026-80874 | Linux kernel 安全漏洞 | |
| CVE-2026-80873 | Linux kernel 安全漏洞 | |
| CVE-2026-80872 | Linux kernel 安全漏洞 | |
| CVE-2026-80871 | Linux kernel 安全漏洞 | |
| CVE-2026-80868 | Linux kernel 安全漏洞 | |
| CVE-2026-80866 | Linux kernel 安全漏洞 | |
| CVE-2026-80867 | Linux kernel 安全漏洞 | |
| CVE-2026-80855 | Linux kernel 安全漏洞 | |
| CVE-2026-80869 | Linux kernel 安全漏洞 |
显示前 20 条，共 156 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-80819
暂无评论