CVE-2026-43194— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于net中GSO帧错误未正确消耗，可能导致连接卡死。
可能的 ATT&CK 技术 1 AI
T1498 · Network Denial of Service影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 1f59533f9ca5634e7b8914252e48aee9d9cbe501< ae3f627b45fbc3c776a4e484696f3cad7cbb4eca |
affected |
1f59533f9ca5634e7b8914252e48aee9d9cbe501< 0c9de092ef8c50a7ee9612811566f0aa81d8d7b6 |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< 56bd32c0edca34041a5c215887fcf562fae2e2db |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< 9ac6aebef4b4bfc5ed408b0b65645981574bc780 |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< ea5d7787635e26ec1194ec7eec0e8e5ae3bd10a5 |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< 4cb163e9efcac4cd35c3043e097f25081a5c015c |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< c86901d22c89a6bf4e2f013e948aaabc60869893 |
affected | ||
1f59533f9ca5634e7b8914252e48aee9d9cbe501< 7aa767d0d3d04e50ae94e770db7db8197f666970 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-43194 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net: consume xmit errors of GSO frames
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net: consume xmit errors of GSO frames
udpgro_frglist.sh and udpgro_bench.sh are the flakiest tests
currently in NIPA. They fail in the same exact way, TCP GRO
test stalls occasionally and the test gets killed after 10min.
These tests use veth to simulate GRO. They attach a trivial
("return XDP_PASS;") XDP program to the veth to force TSO off
and NAPI on.
Digging into the failure mode we can see that the connection
is completely stuck after a burst of drops. The sender's snd_nxt
is at sequence number N [1], but the receiver claims to have
received (rcv_nxt) up to N + 3 * MSS [2]. Last piece of the puzzle
is that senders rtx queue is not empty (let's say the block in
the rtx queue is at sequence number N - 4 * MSS [3]).
In this state, sender sends a retransmission from the rtx queue
with a single segment, and sequence numbers N-4*MSS:N-3*MSS [3].
Receiver sees it and responds with an ACK all the way up to
N + 3 * MSS [2]. But sender will reject this ack as TCP_ACK_UNSENT_DATA
because it has no recollection of ever sending data that far out [1].
And we are stuck.
The root cause is the mess of the xmit return codes. veth returns
an error when it can't xmit a frame. We end up with a loss event
like this:
-------------------------------------------------
| GSO super frame 1 | GSO super frame 2 |
|-----------------------------------------------|
| seg | seg | seg | seg | seg | seg | seg | seg |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
-------------------------------------------------
x ok ok <ok>| ok ok ok <x>
\\
snd_nxt
"x" means packet lost by veth, and "ok" means it went thru.
Since veth has TSO disabled in this test it sees individual segments.
Segment 1 is on the retransmit queue and will be resent.
So why did the sender not advance snd_nxt even tho it clearly did
send up to seg 8? tcp_write_xmit() interprets the return code
from the core to mean that data has not been sent at all. Since
TCP deals with GSO super frames, not individual segment the crux
of the problem is that loss of a single segment can be interpreted
as loss of all. TCP only sees the last return code for the last
segment of the GSO frame (in <> brackets in the diagram above).
Of course for the problem to occur we need a setup or a device
without a Qdisc. Otherwise Qdisc layer disconnects the protocol
layer from the device errors completely.
We have multiple ways to fix this.
1) make veth not return an error when it lost a packet.
While this is what I think we did in the past, the issue keeps
reappearing and it's annoying to debug. The game of whack
a mole is not great.
2) fix the damn return codes
We only talk about NETDEV_TX_OK and NETDEV_TX_BUSY in the
documentation, so maybe we should make the return code from
ndo_start_xmit() a boolean. I like that the most, but perhaps
some ancient, not-really-networking protocol would suffer.
3) make TCP ignore the errors
It is not entirely clear to me what benefit TCP gets from
interpreting the result of ip_queue_xmit()? Specifically once
the connection is established and we're pushing data - packet
loss is just packet loss?
4) this fix
Ignore the rc in the Qdisc-less+GSO case, since it's unreliable.
We already always return OK in the TCQ_F_CAN_BYPASS case.
In the Qdisc-less case let's be a bit more conservative and only
mask the GSO errors. This path is taken by non-IP-"networks"
like CAN, MCTP etc, so we could regress some ancient thing.
This is the simplest, but also maybe the hackiest fix?
Similar fix has been proposed by Eric in the past but never committed
because original reporter was working with an OOT driver and wasn't
providing feedback (see Link).
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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存在安全漏洞，该漏洞源于net中GSO帧错误未正确消耗，可能导致连接卡死。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-43194 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-43194 的情报信息
请登录查看更多情报信息。
CVE-2026-43194 补丁与修复 (8)
同批安全公告 · Linux · 2026-05-06 · 共 224 条
| CVE-2026-43208 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43198 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43186 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43185 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43114 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43197 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43117 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43083 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43239 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43113 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43158 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43232 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43172 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43283 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43176 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43112 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43187 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43249 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43110 | 8.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 224 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-43194
暂无评论