CVE-2026-64177— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于phonet/pep协议中BH处理不当，可能导致不一致的锁状态和自死锁。
可能的 ATT&CK 技术 1 AI
T1059 · Command and Scripting Interpreter影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 9641458d3ec42def729fde64669abf07f3220cd5< f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b |
affected |
9641458d3ec42def729fde64669abf07f3220cd5< b2606c302d7f2b4ee48da05e32ed60aed1b0cd53 |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< 02c04df84de709060f63e1d52ec67488c4f6f212 |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< 8420aa4900417797323dd567ba9d1512280c2dc3 |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< bd795f106b3889fb0706c6e4831c4b27e2b5666b |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< 84bc87beb4cd77670939b446326788e4c9b3db37 |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< a3fc8f2dacd1c37325977fc1fbbf3d52141df99e |
affected | ||
9641458d3ec42def729fde64669abf07f3220cd5< dbc81608e3a653dea6cf403f20cae35468b8ab9c |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-64177 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
phonet/pep: disable BH around forwarded sk_receive_skb()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
phonet/pep: disable BH around forwarded sk_receive_skb()
The networking receive path is usually run from softirq context, but
protocols that take the socket lock may have packets stored in the
backlog and processed later from process context. In that case
release_sock() -> __release_sock() drops the slock with spin_unlock_bh()
and then calls sk->sk_backlog_rcv() with bottom halves enabled.
Typical sk_backlog_rcv handlers process the socket whose backlog is
being drained, so the BH state at entry is irrelevant for the slocks
they touch. pep_do_rcv() is different: when the inbound skb targets an
existing PEP pipe, it forwards the skb to a different *child* socket
via sk_receive_skb(). That helper takes the child slock with
bh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH
is already off. The same child slock therefore ends up acquired with
BH on (process path) and with BH off (softirq path):
process context softirq context
--------------- ---------------
release_sock(listener) __netif_receive_skb()
__release_sock() phonet_rcv()
spin_unlock_bh() __sk_receive_skb(listener)
[BH now ENABLED] [BH already disabled]
sk_backlog_rcv: sk_backlog_rcv:
pep_do_rcv() pep_do_rcv()
sk_receive_skb(child) sk_receive_skb(child)
bh_lock_sock_nested(child) bh_lock_sock_nested(child)
=> SOFTIRQ-ON-W => IN-SOFTIRQ-W
Lockdep flags this as inconsistent lock state, and it can become a real
self-deadlock if a softirq on the same CPU tries to receive to the same
child socket while its slock is held in the BH-enabled path:
WARNING: inconsistent lock state
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
(slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900
__sk_receive_skb net/core/sock.c:563
sk_receive_skb include/net/sock.h:2022 [inline]
pep_do_rcv net/phonet/pep.c:675
sk_backlog_rcv include/net/sock.h:1190
__release_sock net/core/sock.c:3216
release_sock net/core/sock.c:3815
pep_sock_accept net/phonet/pep.c:879
Wrap the forwarded sk_receive_skb() in local_bh_disable() /
local_bh_enable() so the child slock is always acquired with BH off.
local_bh_disable() nests safely on the softirq path.
Discovered via in-house syzkaller fuzzing; the same root cause also
on the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.
Reproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:
https://pastebin.com/A3t8xzCR
来源: 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存在安全漏洞，该漏洞源于phonet/pep协议中BH处理不当，可能导致不一致的锁状态和自死锁。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-64177 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-64177 的情报信息
请登录查看更多情报信息。
CVE-2026-64177 补丁与修复 (8)
同批安全公告 · Linux · 2026-07-19 · 共 429 条
| CVE-2026-63795 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63887 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63994 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64035 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64142 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63993 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-53399 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-53398 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63825 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64025 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64033 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63886 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64091 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63808 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63978 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63979 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64132 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64136 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63800 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
显示前 20 条，共 429 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-64177
暂无评论