CVE-2026-74658— futex: 修复健全文斗退出竞态漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已得到解决： futex：进一步防止健壮 futex 退出时的竞争条件 健壮 futex（robust futex）解锁操作会将整个 futex 值写为 0，从而清除 FUTEX_WAITERS 位，并唤醒单个等待者。该唤醒操作是一次性通知：协议要求接收方要么获取该 futex（并在意识到存在后续竞争的情况下最终解锁），要么在再次休眠之前重新设置 FUTEX_WAITERS 位。如果被唤醒的等待者在执行上述任一操作之前被杀死，内核必须介入并唤醒队列中的下一个任务。 这是 futex
可能的 ATT&CK 技术 1 AI
T1055 · Process Injection影响版本矩阵 30
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | ca16d5bee59807bf04deaab0a8eccecd5061528c< 83b0f71d5a313a765754acab51d2ecc5de76e0b9 |
affected |
ca16d5bee59807bf04deaab0a8eccecd5061528c< a1c2b7b86a946b6b172bce44d74553da2323a36c |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< 33bfa85458105d6169ebdb697f692b8bb8025bae |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< aa5c571901c6b22b58373693a4bf889ecab11ff5 |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< 925628656b73b70930972ccde421de4f758d8650 |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< 7b8c53263f8878bdd12c87e147ac6feca5c05211 |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< 7cf710e70f9bb8ea75f759ebed09871801315992 |
affected | ||
ca16d5bee59807bf04deaab0a8eccecd5061528c< 6d4514ca9cdf61fec4ec634cf50386f6f7e69748 |
affected | ||
| … +22 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-74658 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
futex: Prevent robust futex exit race some more
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
futex: Prevent robust futex exit race some more
A robust futex unlock stores 0 over the whole futex value - wiping
FUTEX_WAITERS - and wakes a single waiter. That wakeup is a one-shot
notification: the protocol relies on its recipient to either acquire the
futex (and eventually unlock while aware of the remaining contention) or
re-arm FUTEX_WAITERS before sleeping again. If the woken waiter is killed
before it can do either, the kernel must jump in and wake the next task
down the line.
This is a known complication of the futex protocol with a previous
partial fix in commit ca16d5bee598 ("futex: Prevent robust futex exit
race"). Unfortunately, that fix is insufficient.
If a third task re-acquired the futex through the uncontended fast
path in the meantime, the notification is lost: robust exit processing
sees that it is owned by another task and does nothing, while the new
owner sees no FUTEX_WAITERS when it unlocks and wakes nobody.
The remaining waiters sleep forever behind a free futex:
A owns the futex, B and C sleep in FUTEX_WAIT
uval == A | FUTEX_WAITERS
A robust unlock: store 0, FUTEX_WAKE(1) wakes B
uval == 0
D fast path acquire: cmpxchg(0 -> D)
uval == D, no FUTEX_WAITERS
B killed before acting on the wakeup
B exit walk, pending op: owner D != B -> no action
D unlock: no FUTEX_WAITERS -> no wake
C sleeps forever
This is clearly a shortcoming in the implementation, which fails to keep
the FUTEX_WAITERS bit consistent.
Work around this by augmenting the robust list exit processing to also
perform the extra wakeup if the futex word is owned by another thread but
FUTEX_WAITERS is not set.
This does not fix the problem of a non-contended take over/release and free
sequence, which has been discussed for years and has been addressed by
commit 3ca9595d9fb6 ("futex: Add support for unlocking robust futexes") and
subsequent changes, but failed to take the problem described above into
account.
A more complete solution which is based on the in kernel unlock of
contended robust futexes has been discussed in the context of this change
and should show up in mainline sooner than later.
[ tglx: Amend change log slightly and fixup coding style ]
来源: 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-74658 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-74658 的情报信息
请登录查看更多情报信息。
CVE-2026-74658 补丁与修复 (7)
同批安全公告 · Linux · 2026-08-22 · 共 150 条
| CVE-2026-74705 | 10.0 CRITICAL | UDP隧道分段潜在使用-after-free漏洞 |
| CVE-2026-74612 | 10.0 CRITICAL | Linux内核veth模块SKB长度计算漏洞 |
| CVE-2026-74588 | 9.8 CRITICAL | Linux SCTP传输列表不同步漏洞 |
| CVE-2026-74628 | 9.8 CRITICAL | Linux内核 x25 远程计时器释放后使用漏洞 |
| CVE-2026-74669 | 9.8 CRITICAL | Linux IPVS IPv4选项后重定位隧道ICMP错误 |
| CVE-2026-74597 | 9.8 CRITICAL | Linux ip6_tunnel skb2->cb[]未清除漏洞 |
| CVE-2026-74608 | 9.8 CRITICAL | SMB客户端cifs_try_adding_channels函数中的释放后使用漏洞 |
| CVE-2026-74662 | 9.8 CRITICAL | Linux inet frags 定时器竞争条件漏洞 |
| CVE-2026-74611 | 9.8 CRITICAL | TLS 1.3 乐观重试消息迭代器恢复漏洞 |
| CVE-2026-74587 | 9.8 CRITICAL | SCTP 缓存 ASCONF 块使用后释放漏洞 |
| CVE-2026-74688 | 9.8 CRITICAL | SCTP传输控制块移除漏洞 |
| CVE-2026-74723 | 9.8 CRITICAL | btrfs LZO拒绝无有效头部的内联扩展 |
| CVE-2026-74616 | 9.8 CRITICAL | Linux内核XDP克隆数据包越界漏洞 |
| CVE-2026-74591 | 9.8 CRITICAL | Linux 内核文件映射恢复索引前重试导致漏洞 |
| CVE-2026-74586 | 9.8 CRITICAL | Linux内核SCTP对等端移除时传输未清理漏洞 |
| CVE-2026-74727 | 9.8 CRITICAL | OpenVPN by_id移除后跳过哈希重构 |
| CVE-2026-74617 | 9.8 CRITICAL | dibs: 在dibs_dev_alloc()中初始化dibs->lock |
| CVE-2026-74730 | 9.8 CRITICAL | NFS：在FREE_STATEID调用期间锁定struct nfs_server |
| CVE-2026-74712 | 9.3 CRITICAL | mlx5 vdpa 在 create_direct_keys() 中缓冲区长度修复漏洞 |
| CVE-2026-74665 | 9.1 CRITICAL | NET skb长度计算通用XDP片段调整后修复 |
显示前 20 条，共 150 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-74658
暂无评论