CVE-2024-26608

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: fix global oob in ksmbd_nl_policy<br /> <br /> Similar to a reported issue (check the commit b33fb5b801c6 ("net:<br /> qualcomm: rmnet: fix global oob in rmnet_policy"), my local fuzzer finds<br /> another global out-of-bounds read for policy ksmbd_nl_policy. See bug<br /> trace below:<br /> <br /> ==================================================================<br /> BUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:386 [inline]<br /> BUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600<br /> Read of size 1 at addr ffffffff8f24b100 by task syz-executor.1/62810<br /> <br /> CPU: 0 PID: 62810 Comm: syz-executor.1 Tainted: G N 6.1.0 #3<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0x8b/0xb3 lib/dump_stack.c:106<br /> print_address_description mm/kasan/report.c:284 [inline]<br /> print_report+0x172/0x475 mm/kasan/report.c:395<br /> kasan_report+0xbb/0x1c0 mm/kasan/report.c:495<br /> validate_nla lib/nlattr.c:386 [inline]<br /> __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600<br /> __nla_parse+0x3e/0x50 lib/nlattr.c:697<br /> __nlmsg_parse include/net/netlink.h:748 [inline]<br /> genl_family_rcv_msg_attrs_parse.constprop.0+0x1b0/0x290 net/netlink/genetlink.c:565<br /> genl_family_rcv_msg_doit+0xda/0x330 net/netlink/genetlink.c:734<br /> genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]<br /> genl_rcv_msg+0x441/0x780 net/netlink/genetlink.c:850<br /> netlink_rcv_skb+0x14f/0x410 net/netlink/af_netlink.c:2540<br /> genl_rcv+0x24/0x40 net/netlink/genetlink.c:861<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]<br /> netlink_unicast+0x54e/0x800 net/netlink/af_netlink.c:1345<br /> netlink_sendmsg+0x930/0xe50 net/netlink/af_netlink.c:1921<br /> sock_sendmsg_nosec net/socket.c:714 [inline]<br /> sock_sendmsg+0x154/0x190 net/socket.c:734<br /> ____sys_sendmsg+0x6df/0x840 net/socket.c:2482<br /> ___sys_sendmsg+0x110/0x1b0 net/socket.c:2536<br /> __sys_sendmsg+0xf3/0x1c0 net/socket.c:2565<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> RIP: 0033:0x7fdd66a8f359<br /> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48<br /> RSP: 002b:00007fdd65e00168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e<br /> RAX: ffffffffffffffda RBX: 00007fdd66bbcf80 RCX: 00007fdd66a8f359<br /> RDX: 0000000000000000 RSI: 0000000020000500 RDI: 0000000000000003<br /> RBP: 00007fdd66ada493 R08: 0000000000000000 R09: 0000000000000000<br /> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000<br /> R13: 00007ffc84b81aff R14: 00007fdd65e00300 R15: 0000000000022000<br /> <br /> <br /> The buggy address belongs to the variable:<br /> ksmbd_nl_policy+0x100/0xa80<br /> <br /> The buggy address belongs to the physical page:<br /> page:0000000034f47940 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1ccc4b<br /> flags: 0x200000000001000(reserved|node=0|zone=2)<br /> raw: 0200000000001000 ffffea00073312c8 ffffea00073312c8 0000000000000000<br /> raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000<br /> page dumped because: kasan: bad access detected<br /> <br /> Memory state around the buggy address:<br /> ffffffff8f24b000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> ffffffff8f24b080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> &gt;ffffffff8f24b100: f9 f9 f9 f9 00 00 f9 f9 f9 f9 f9 f9 00 00 07 f9<br /> ^<br /> ffffffff8f24b180: f9 f9 f9 f9 00 05 f9 f9 f9 f9 f9 f9 00 00 00 05<br /> ffffffff8f24b200: f9 f9 f9 f9 00 00 03 f9 f9 f9 f9 f9 00 00 04 f9<br /> ==================================================================<br /> <br /> To fix it, add a placeholder named __KSMBD_EVENT_MAX and let<br /> KSMBD_EVENT_MAX to be its original value - 1 according to what other<br /> netlink families do. Also change two sites that refer the<br /> KSMBD_EVENT_MAX to correct value.