CVE-2026-46275— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于蓝牙hci_uart的关闭和初始化路径中存在释放后重用和竞争条件，可能导致空指针取消引用。
影响版本矩阵 28
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 3b799254cf6f481460719023d7a18f46651e5e7f< 78aad93e938f013d9272fe0ee168f27883afa95c |
affected |
3b799254cf6f481460719023d7a18f46651e5e7f< e2d19969c8d9198ecc3090bcd5312ecd503a3339 |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< c85cff648a2bc92322912db5f1727ad05afae7b6 |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< 9d20d48be2c4a071fb015eb09bda2cecd25daf34 |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< 81c7a3c22a0f2808cf4ae0b4908f59763b23606d |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< 192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894 |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< 7338031946bd06f6dff149e67b60c4cd083bfea8 |
affected | ||
3b799254cf6f481460719023d7a18f46651e5e7f< c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b |
affected | ||
| … +20 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-46275 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths
Vulnerabilities leading to Use-After-Free (UAF) and Null Pointer
Dereference (NPD) conditions were observed in the lifecycle management
of hci_uart.
The primary issue arises because the workqueues (init_ready and
write_work) are only flushed/cancelled if the HCI_UART_PROTO_READY
flag is set during TTY close. If a hangup occurs before setup completes,
hci_uart_tty_close() skips the teardown of these workqueues and
proceeds to free the `hu` struct. When the scheduled work executes
later, it blindly dereferences the freed `hu` struct.
Furthermore, several data races and UAFs were identified in the teardown
sequence:
1. Calling hci_uart_flush() from hci_uart_close() without effectively
disabling write_work causes a race condition where both can concurrently
double-free hu->tx_skb. This happens because protocol timers can
concurrently invoke hci_uart_tx_wakeup() and requeue write_work.
2. Calling hci_free_dev(hdev) before hu->proto->close(hu) causes a UAF
when vendor specific protocol close callbacks dereference hu->hdev.
3. In the initialization error paths, failing to take the proto_lock
write lock before clearing PROTO_READY leads to races with active
readers. Additionally, hci_uart_tty_receive() accesses hu->hdev
outside the read lock, leading to UAFs if the initialization error
path frees hdev concurrently.
Fix these synchronization and lifecycle issues by:
1. Re-ordering hci_uart_tty_close() to clear HCI_UART_PROTO_READY first,
followed immediately by a cancel_work_sync(&hu->write_work). Clearing
the flag locks out concurrent protocol timers from successfully invoking
hci_uart_tx_wakeup(), effectively rendering the cancellation permanent
and preventing the tx_skb double-free.
2. Note: Clearing PROTO_READY early causes hci_uart_close() to skip
hu->proto->flush(). This is perfectly safe in the tty_close path
because hu->proto->close() executes shortly after, which intrinsically
purges all protocol SKB queues and tears down the state.
3. Relocating hu->proto->close(hu) strictly prior to hci_free_dev(hdev)
across all close and error paths to prevent vendor-level UAFs.
4. Moving the hdev->stat.byte_rx increment in hci_uart_tty_receive()
inside the proto_lock read-side critical section to safely synchronize
with device unregistration.
5. Adding cancel_work_sync(&hu->write_work) to hci_uart_close() to safely
flush the workqueue before hci_uart_flush() is invoked via the HCI core.
6. Utilizing cancel_work_sync() instead of disable_work_sync() across
all paths to prevent permanently breaking user-space retry capabilities.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: 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所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于蓝牙hci_uart的关闭和初始化路径中存在释放后重用和竞争条件，可能导致空指针取消引用。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-46275 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-46275 的情报信息
请登录查看更多情报信息。
CVE-2026-46275 补丁与修复 (7)
同批安全公告 · Linux · 2026-06-08 · 共 41 条
| CVE-2026-46289 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-46288 | 8.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46307 | 8.3 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46303 | 8.2 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46274 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46311 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46280 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46277 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46306 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46304 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46299 | 7.0 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-46296 | Linux kernel 安全漏洞 | |
| CVE-2026-46298 | Linux kernel 安全漏洞 | |
| CVE-2026-46301 | Linux kernel 安全漏洞 | |
| CVE-2026-46302 | Linux kernel 安全漏洞 | |
| CVE-2026-46314 | Linux kernel 安全漏洞 | |
| CVE-2025-71315 | Linux kernel 安全漏洞 | |
| CVE-2026-46305 | Linux kernel 安全漏洞 | |
| CVE-2026-46313 | Linux kernel 安全漏洞 | |
| CVE-2026-46308 | Linux kernel 安全漏洞 |
显示前 20 条，共 41 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-46275
暂无评论