CVE-2024-26804— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞，该漏洞源于 net ip_tunnel中存在安全问题。
可能的 ATT&CK 技术 1 AI
T1498.001 · Direct Network Flood影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 243aad830e8a4cdda261626fbaeddde16b08d04a< f81e94d2dcd2397137edcb8b85f4c5bed5d22383 |
affected |
243aad830e8a4cdda261626fbaeddde16b08d04a< 2e95350fe9db9d53c701075060ac8ac883b68aee |
affected | ||
243aad830e8a4cdda261626fbaeddde16b08d04a< afec0c5cd2ed71ca95a8b36a5e6d03333bf34282 |
affected | ||
243aad830e8a4cdda261626fbaeddde16b08d04a< ab63de24ebea36fe73ac7121738595d704b66d96 |
affected | ||
243aad830e8a4cdda261626fbaeddde16b08d04a< a0a1db40b23e8ff86dea2786c5ea1470bb23ecb9 |
affected | ||
243aad830e8a4cdda261626fbaeddde16b08d04a< 049d7989c67e8dd50f07a2096dbafdb41331fb9b |
affected | ||
243aad830e8a4cdda261626fbaeddde16b08d04a< 5ae1e9922bbdbaeb9cfbe91085ab75927488ac0f |
affected | ||
03017375b0122453e6dda833ff7bd4191915def5 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-26804 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net: ip_tunnel: prevent perpetual headroom growth
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net: ip_tunnel: prevent perpetual headroom growth
syzkaller triggered following kasan splat:
BUG: KASAN: use-after-free in __skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170
Read of size 1 at addr ffff88812fb4000e by task syz-executor183/5191
[..]
kasan_report+0xda/0x110 mm/kasan/report.c:588
__skb_flow_dissect+0x19d1/0x7a50 net/core/flow_dissector.c:1170
skb_flow_dissect_flow_keys include/linux/skbuff.h:1514 [inline]
___skb_get_hash net/core/flow_dissector.c:1791 [inline]
__skb_get_hash+0xc7/0x540 net/core/flow_dissector.c:1856
skb_get_hash include/linux/skbuff.h:1556 [inline]
ip_tunnel_xmit+0x1855/0x33c0 net/ipv4/ip_tunnel.c:748
ipip_tunnel_xmit+0x3cc/0x4e0 net/ipv4/ipip.c:308
__netdev_start_xmit include/linux/netdevice.h:4940 [inline]
netdev_start_xmit include/linux/netdevice.h:4954 [inline]
xmit_one net/core/dev.c:3548 [inline]
dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564
__dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4349
dev_queue_xmit include/linux/netdevice.h:3134 [inline]
neigh_connected_output+0x42c/0x5d0 net/core/neighbour.c:1592
...
ip_finish_output2+0x833/0x2550 net/ipv4/ip_output.c:235
ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323
..
iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82
ip_tunnel_xmit+0x1dbc/0x33c0 net/ipv4/ip_tunnel.c:831
ipgre_xmit+0x4a1/0x980 net/ipv4/ip_gre.c:665
__netdev_start_xmit include/linux/netdevice.h:4940 [inline]
netdev_start_xmit include/linux/netdevice.h:4954 [inline]
xmit_one net/core/dev.c:3548 [inline]
dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3564
...
The splat occurs because skb->data points past skb->head allocated area.
This is because neigh layer does:
__skb_pull(skb, skb_network_offset(skb));
... but skb_network_offset() returns a negative offset and __skb_pull()
arg is unsigned. IOW, we skb->data gets "adjusted" by a huge value.
The negative value is returned because skb->head and skb->data distance is
more than 64k and skb->network_header (u16) has wrapped around.
The bug is in the ip_tunnel infrastructure, which can cause
dev->needed_headroom to increment ad infinitum.
The syzkaller reproducer consists of packets getting routed via a gre
tunnel, and route of gre encapsulated packets pointing at another (ipip)
tunnel. The ipip encapsulation finds gre0 as next output device.
This results in the following pattern:
1). First packet is to be sent out via gre0.
Route lookup found an output device, ipip0.
2).
ip_tunnel_xmit for gre0 bumps gre0->needed_headroom based on the future
output device, rt.dev->needed_headroom (ipip0).
3).
ip output / start_xmit moves skb on to ipip0. which runs the same
code path again (xmit recursion).
4).
Routing step for the post-gre0-encap packet finds gre0 as output device
to use for ipip0 encapsulated packet.
tunl0->needed_headroom is then incremented based on the (already bumped)
gre0 device headroom.
This repeats for every future packet:
gre0->needed_headroom gets inflated because previous packets' ipip0 step
incremented rt->dev (gre0) headroom, and ipip0 incremented because gre0
needed_headroom was increased.
For each subsequent packet, gre/ipip0->needed_headroom grows until
post-expand-head reallocations result in a skb->head/data distance of
more than 64k.
Once that happens, skb->network_header (u16) wraps around when
pskb_expand_head tries to make sure that skb_network_offset() is unchanged
after the headroom expansion/reallocation.
After this skb_network_offset(skb) returns a different (and negative)
result post headroom expansion.
The next trip to neigh layer (or anything else that would __skb_pull the
network header) makes skb->data point to a memory location outside
skb->head area.
v2: Cap the needed_headroom update to an arbitarily chosen upperlimit to
prevent perpetual increase instead of dropping the headroom increment
completely.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 ip_tunnel中存在安全问题。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-26804 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-26804 的情报信息
请登录查看更多情报信息。
CVE-2024-26804 邮件列表归档 (1)
CVE-2024-26804 其他参考 (7)
同批安全公告 · Linux · 2024-04-04 · 共 32 条
| CVE-2024-26782 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-26800 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-26801 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26792 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26809 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26808 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26807 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26802 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26797 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26795 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26793 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26789 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26786 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26799 | 7.0 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-26746 | Linux kernel 安全漏洞 | |
| CVE-2024-26788 | Linux kernel 安全漏洞 | |
| CVE-2024-26750 | Linux kernel 安全漏洞 | |
| CVE-2024-26780 | Linux kernel 安全漏洞 | |
| CVE-2024-26806 | Linux kernel 安全漏洞 | |
| CVE-2024-26805 | Linux kernel 安全漏洞 |
显示前 20 条，共 32 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-26804
暂无评论