CVE-2026-98070— Linux RDS 模块远程代码执行漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已修复以下漏洞： net/rds：在 中正确获取 状态 通过将路径状态设置为 来使发送路径静默（quiesce），然后等待 位被采样为清除状态（即 0），之后才交换底层 socket 并调用 。 然而，“采样清除位”并不等同于“拥有该位”：在 返回后， 可能会重新获取 位。由于采用锁后的状态重检是一种存储缓冲模式（resetter 写入状态并读取位，sender 写入位并读取状态），且 仅是一个获取操作（acquire operation），因此在弱排序架构上，双方都可能错过对方的写操作，导
可能的 ATT&CK 技术 1 AI
T1055 · Process Injection影响版本矩阵 10
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 335b48d980f631fbc5b233cbb3625ac0c86d67cb< d625112564c3e980e02504270222b49b82690cee |
affected |
335b48d980f631fbc5b233cbb3625ac0c86d67cb< 8e4c3b7844c906c7097b4cfedd9dd1f48c9a6a92 |
affected | ||
335b48d980f631fbc5b233cbb3625ac0c86d67cb< 062d9e008c67289e8e1b221ecdd8f9d60566d012 |
affected | ||
335b48d980f631fbc5b233cbb3625ac0c86d67cb< 02c5f9dc2efd823e061954d564ce00bacd1bebeb |
affected | ||
4.7 |
affected | ||
< 4.7 |
unaffected | ||
6.12.111≤ 6.12.* |
unaffected | ||
6.18.53≤ 6.18.* |
unaffected | ||
| … +2 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-98070 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks()
rds_tcp_reset_callbacks() quiesces the transmit path by setting the
path state to RDS_CONN_RESETTING and then waiting for RDS_IN_XMIT to
be sampled clear before swapping the underlying socket and calling
rds_send_path_reset().
Sampling the bit clear is not the same as owning it: rds_send_xmit()
can re-acquire RDS_IN_XMIT right after the wait_event() returns. Its
state recheck after taking the lock is a store-buffering pattern (the
resetter writes the state and reads the bit, the sender writes the
bit and reads the state) and acquire_in_xmit() is only an acquire
operation, so on weakly ordered architectures both sides can miss
each other's write and the transmit path then runs concurrently with
rds_send_path_reset() rewriting cp_xmit_* state - which is exactly
what the comment above rds_send_path_reset() tells its callers to
prevent.
Take the lock instead, hold it across the socket swap and
rds_send_path_reset(), and release it with a wake-up at the end. The
lock-ordering constraint documented above the wait still holds: the
lock is acquired before lock_sock(), so a sender inside tcp_sendmsg()
can never be waited on while we hold the socket lock.
Two details of the old code go away with the same change:
- t_sock is now read only after the lock is acquired. The old code
cached it before waiting; the teardown in rds_conn_shutdown()
releases that socket and clears t_sock, so a pointer cached before
the wait can be stale by the time the accept path resumes. Reading
it under RDS_IN_XMIT is what makes the exclusion complete once the
teardown owns the same lock, which the next patch arranges; until
then the teardown still only samples the bit, and the two paths
remain as exposed to each other as they are today.
- The old !osock early path called rds_send_path_reset() with no
serialization at all. It now runs under the lock like the normal
path. The conditional RDS_CONN_RESETTING transition of the
previous patch happens before the socket check either way: a path
found without a socket is either still connecting (its reconnect
worker blocked on t_conn_path_lock) and legitimately goes
RESETTING -> UP on the new socket, or it has been torn down
meanwhile and is dropped.
The in-function comment describing the old wait-based quiesce is
rewritten to describe the lock-based one, and the stale block comment
above the function (which still described a return value and an
incomplete list of t_sock writers) is refreshed to name all four
writers - the connect, accept, teardown and swap paths - and what
serializes each of them.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-98070 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-98070 的情报信息
请登录查看更多情报信息。
CVE-2026-98070 补丁与修复 (4)
同批安全公告 · Linux · 2026-09-25 · 共 372 条
| CVE-2026-100075 | 9.8 CRITICAL | RDMA/srpt：srpt_alloc_rw_ctxs() 未释放计数器修复 |
| CVE-2026-97555 | 8.8 HIGH | smb客户端：修复DACL所有者/组重写中的堆溢出漏洞 |
| CVE-2026-97957 | 8.8 HIGH | hinic 邮箱段缓冲区溢出漏洞 |
| CVE-2026-97527 | 8.8 HIGH | qla2xxx SCSI驱动程序 NVMe未解决上下文列表竞争条件漏洞 |
| CVE-2026-97528 | 8.8 HIGH | QLogic qla2xxx驱动LS拒绝错误NVMe内存泄漏漏洞 |
| CVE-2026-98115 | 8.8 HIGH | ksmbd 注销期间会话安全排空漏洞 |
| CVE-2026-97525 | 8.2 HIGH | x86/mm/pat：内核页表分裂页表分配漏洞 |
| CVE-2026-98069 | 8.1 HIGH | Net/RDS rds_conn_shutdown() 快速路径锁获取漏洞 |
| CVE-2026-97573 | 8.1 HIGH | bnxt_en 驱动 bnxt_rx_ring_reset 缓冲区分配失败漏洞 |
| CVE-2026-97570 | 8.1 HIGH | bnxt_en: 修复因SW TPA ID绑定问题导致的崩溃漏洞 |
| CVE-2026-98130 | 8.1 HIGH | SCTP定时器启动竞争条件漏洞 |
| CVE-2026-98122 | 7.8 HIGH | Linux内核vxlan mdb远程源删除后使用漏洞 |
| CVE-2026-97575 | 7.8 HIGH | v4l2-ctrls AV1瓦片计数验证漏洞 |
| CVE-2026-97576 | 7.8 HIGH | V4L2-ctrls HEVC 瓦片计数验证漏洞 |
| CVE-2026-98112 | 7.8 HIGH | ksmbd 网络接口事件中监听器任务生命周期修复漏洞 |
| CVE-2026-98002 | 7.8 HIGH | AMD IOMMU 嵌套域分配中错误检查失效漏洞 |
| CVE-2026-97937 | 7.8 HIGH | Linux内核ftrace远程代码执行漏洞 |
| CVE-2026-97940 | 7.8 HIGH | IPv6 修复 fib6 遍历器在 seq 停止时存在 UAF 漏洞 |
| CVE-2026-98116 | 7.8 HIGH | ALSA: PCM内存映射与缓冲区重新分配序列化以修复页面UAF漏洞 |
| CVE-2026-97578 | 7.8 HIGH | Verisilicon VPU981 AV1除数和瓦片缓冲区保护漏洞 |
显示前 20 条，共 372 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-98070
暂无评论