Shigeru Yoshida
ddbec99f58
hsr: Fix uninit-value access in hsr_get_node()
...
KMSAN reported the following uninit-value access issue [1]:
=====================================================
BUG: KMSAN: uninit-value in hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246
hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246
fill_frame_info net/hsr/hsr_forward.c:577 [inline]
hsr_forward_skb+0xe12/0x30e0 net/hsr/hsr_forward.c:615
hsr_dev_xmit+0x1a1/0x270 net/hsr/hsr_device.c:223
__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+0x247/0xa10 net/core/dev.c:3564
__dev_queue_xmit+0x33b8/0x5130 net/core/dev.c:4349
dev_queue_xmit include/linux/netdevice.h:3134 [inline]
packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276
packet_snd net/packet/af_packet.c:3087 [inline]
packet_sendmsg+0x8b1d/0x9f30 net/packet/af_packet.c:3119
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg net/socket.c:745 [inline]
__sys_sendto+0x735/0xa10 net/socket.c:2191
__do_sys_sendto net/socket.c:2203 [inline]
__se_sys_sendto net/socket.c:2199 [inline]
__x64_sys_sendto+0x125/0x1c0 net/socket.c:2199
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
Uninit was created at:
slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768
slab_alloc_node mm/slub.c:3478 [inline]
kmem_cache_alloc_node+0x5e9/0xb10 mm/slub.c:3523
kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:560
__alloc_skb+0x318/0x740 net/core/skbuff.c:651
alloc_skb include/linux/skbuff.h:1286 [inline]
alloc_skb_with_frags+0xc8/0xbd0 net/core/skbuff.c:6334
sock_alloc_send_pskb+0xa80/0xbf0 net/core/sock.c:2787
packet_alloc_skb net/packet/af_packet.c:2936 [inline]
packet_snd net/packet/af_packet.c:3030 [inline]
packet_sendmsg+0x70e8/0x9f30 net/packet/af_packet.c:3119
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg net/socket.c:745 [inline]
__sys_sendto+0x735/0xa10 net/socket.c:2191
__do_sys_sendto net/socket.c:2203 [inline]
__se_sys_sendto net/socket.c:2199 [inline]
__x64_sys_sendto+0x125/0x1c0 net/socket.c:2199
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
CPU: 1 PID: 5033 Comm: syz-executor334 Not tainted 6.7.0-syzkaller-00562-g9f8413c4a66f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
=====================================================
If the packet type ID field in the Ethernet header is either ETH_P_PRP or
ETH_P_HSR, but it is not followed by an HSR tag, hsr_get_skb_sequence_nr()
reads an invalid value as a sequence number. This causes the above issue.
This patch fixes the issue by returning NULL if the Ethernet header is not
followed by an HSR tag.
Fixes: f266a683a480 ("net/hsr: Better frame dispatch")
Reported-and-tested-by: syzbot+2ef3a8ce8e91b5a50098@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=2ef3a8ce8e91b5a50098 [1]
Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
Link: https://lore.kernel.org/r/20240312152719.724530-1-syoshida@redhat.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2024-03-14 13:02:51 +01:00
..
2024-02-09 14:12:01 -08:00
2023-12-13 05:44:30 +09:00
2024-02-26 11:46:12 +00:00
2023-12-26 20:31:01 +00:00
2024-02-09 14:12:01 -08:00
2024-02-02 12:44:16 +00:00
2024-03-08 11:06:14 -05:00
2024-03-11 18:06:04 -07:00
2024-02-29 14:24:56 -08:00
2024-01-05 08:06:35 -08:00
2024-02-20 15:32:45 +01:00
2024-03-06 12:43:01 +01:00
2024-03-12 17:44:08 -07:00
2024-02-02 12:19:26 +00:00
2024-03-13 08:31:40 +00:00
2024-01-11 10:07:29 -08:00
2024-03-07 20:37:13 -08:00
2024-03-06 20:40:20 -08:00
2024-02-08 18:32:29 -08:00
2024-03-14 13:02:51 +01:00
2024-03-08 20:35:33 -08:00
2023-12-15 10:50:18 +00:00
2024-03-14 10:57:02 +01:00
2024-03-11 20:38:36 -07:00
2024-02-22 18:28:13 -08:00
2024-03-11 09:53:22 +00:00
2024-02-09 14:12:01 -08:00
2024-03-11 09:53:22 +00:00
2024-01-30 13:49:09 +01:00
2024-03-08 09:05:49 -08:00
2024-03-06 21:01:26 +01:00
2024-02-29 14:24:56 -08:00
2024-03-07 20:42:13 -08:00
2024-03-11 10:37:40 +00:00
2024-03-12 17:44:08 -07:00
2024-02-28 19:37:34 -08:00
2024-03-11 15:48:34 -07:00
2024-03-07 10:36:58 +01:00
2024-03-05 11:21:18 -08:00
2024-02-09 12:54:38 -08:00
2024-03-11 15:52:05 -07:00
2024-02-22 09:05:50 +01:00
2023-12-29 08:43:59 +00:00
2024-01-01 18:41:29 +00:00
2024-03-07 10:29:36 -08:00
2023-12-21 22:17:23 +01:00
2023-12-15 11:59:53 +00:00
2024-03-05 23:35:26 +00:00
2024-03-13 08:26:42 +00:00
2024-03-07 21:12:43 -08:00
2024-03-05 15:49:35 +01:00
2024-03-01 09:12:30 -05:00
2024-02-16 09:36:37 +00:00
2024-02-15 13:18:19 +01:00
2024-02-29 09:07:16 -08:00
2024-02-22 15:29:26 -08:00
2024-01-23 15:13:54 +01:00
2024-03-08 09:05:49 -08:00
2024-03-11 09:53:22 +00:00
2024-03-02 20:50:59 -08:00
2024-03-08 10:56:05 +00:00
2023-12-12 14:24:14 +01:00
2024-02-18 10:19:21 +00:00
2024-01-31 16:41:16 -08:00
2024-02-28 19:29:46 -08:00