CVE-2026-98022— 网络子系统S16_MAX限制tx_queue_len防溢出
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已解决以下漏洞： 网络子系统：将 tx_queue_len 上限限制为 S16_MAX，以防止分配过大的环缓冲区 多个子系统通过 来分配环缓冲区大小，且未设置上限。特权较低的恶意用户（通过 命令）可以设置一个巨大的 值，从而导致通过环缓冲区分配耗尽全局内存。具体涉及的子系统包括： pfifo_fast： 和 会分别分配包含 个条目的 3 个 环。 tun： 以及在 NETDEV_CHANGE_TX_QUEUE_LEN 通知器触发时的队列附加路径，会将 调整大小为 。 tap（包括 macvt
可能的 ATT&CK 技术 1 AI
T1496 · Resource Hijacking影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< 24d02c909a1725ab9eceb92db7d02e4e841f17ca |
affected |
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< 5e5591a0f33f7c11bf1d338dbb6c5072575de64c |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< c8d4060610c69645733c92d94fceb4b93808ac4d |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< c2362c500931e5bd1826bce34e9ce28af80e7541 |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< 81c0e02076989743a603806a5a4f44d2c40dc01f |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< 081340cf70a789b94b4174af54a63ffd49677a4e |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< a03b927bae4af5c23fd5315a237855c17cc8f422 |
affected | ||
6a643ddb5624be7e0694d49f5765a8d41c1ab6d0< 66ab4c59b74db7ab53a1c9083feaaede393a96a0 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-98022 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations
Several subsystems allocate ring buffers sized by dev->tx_queue_len
with no upper bound. An unprivileged user (via unshare -Urn) can set a
huge tx_queue_len and exhaust global memory with ring allocations:
- pfifo_fast: pfifo_fast_init() and pfifo_fast_change_tx_queue_len()
allocate 3 skb_array rings of tx_queue_len entries each.
- tun: tun_queue_resize() and the queue-attach path resize ptr_rings
to tx_queue_len on the NETDEV_CHANGE_TX_QUEUE_LEN notifier.
- tap (macvtap/ipvtap): tap_queue_resize() and tap_init() resize/init
ptr_rings to tx_queue_len on the same notifier.
netif_change_tx_queue_len() is the single entry point for IFLA_TXQLEN,
sysfs, and the SIOCSIFTXQLEN ioctl. Cap new_len at S16_MAX (32767)
there so the oversized value is rejected at set time. This takes
effect whether the device is up or down, before dev->tx_queue_len is
written, before any notifier fires, and before any ring is allocated.
The "> S16_MAX" check also subsumes the previous unsigned-long
truncation test, and a negative ifr_qlen from the ioctl lands far
above the cap after conversion, so both old failure modes are covered
by the one comparison.
tx_queue_len is ambigious: both a per-ring sizing multiplier and a
default queue-length/limit knob for consumers that allocate
nothing at set time (pfifo/bfifo/gred/plug/sfb limits, htb
direct_qlen, qfq max_classes, teql). 32767 is chosen as the largest
value NLA_POLICY_FULL_RANGE can express for the u32 IFLA_TXQLEN
policy in patch 2/3 while staying a legitimate queue length on
high-BDP paths; the ring-memory trade-off of a shared knob is
disclosed below.
Conditions to recreate the bug:
- CONFIG_NET_SCHED=y, CONFIG_VETH=y, CONFIG_USER_NS=y, CONFIG_NET_NS=y.
- Unprivileged user in a fresh user+net namespace (unshare -Urn).
- pfifo_fast: create veth pairs, set tx_queue_len to 500000, attach
mq+pfifo_fast. ~28 iterations OOMs a 2GB guest.
- tun: create 50 tun devices with IFF_MULTI_QUEUE, set tx_queue_len to
500000, open 8 queues each. ~1.6GB of ptr_ring allocations OOMs a
512MB guest.
- tap: same as tun with IFF_TAP. ~960MB OOMs a 512MB guest.
- On the fixed kernel the oversized tx_queue_len is rejected with
-ERANGE at set time (all four paths: RTM_SETLINK, RTM_NEWLINK
create, sysfs, ioctl - the latter two via this check, the former
two via this check and the 2/3 parse policy respectively).
来源: 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-98022 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-98022 的情报信息
请登录查看更多情报信息。
CVE-2026-98022 补丁与修复 (8)
同批安全公告 · 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-98070 | 8.1 HIGH | Linux RDS 模块远程代码执行漏洞 |
| CVE-2026-98002 | 7.8 HIGH | AMD IOMMU 嵌套域分配中错误检查失效漏洞 |
| CVE-2026-97575 | 7.8 HIGH | v4l2-ctrls AV1瓦片计数验证漏洞 |
| CVE-2026-97576 | 7.8 HIGH | V4L2-ctrls HEVC 瓦片计数验证漏洞 |
| CVE-2026-97941 | 7.8 HIGH | Linux 内核 slab 内存分配器竞态条件漏洞 |
| CVE-2026-98112 | 7.8 HIGH | ksmbd 网络接口事件中监听器任务生命周期修复漏洞 |
| CVE-2026-97937 | 7.8 HIGH | Linux内核ftrace远程代码执行漏洞 |
| CVE-2026-97580 | 7.8 HIGH | rkvdec HEVC解析数组越界漏洞 |
| CVE-2026-97940 | 7.8 HIGH | IPv6 修复 fib6 遍历器在 seq 停止时存在 UAF 漏洞 |
显示前 20 条，共 372 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-98022
暂无评论