1. 07 7月, 2023 38 次提交
  2. 06 7月, 2023 2 次提交
    • Y
      ipmi_si: fix a memleak in try_smi_init() · 18b2bde9
      Yi Yang 提交于
      maillist inclusion
      category: bugfix
      bugzilla: https://gitee.com/openeuler/kernel/issues/I7GMNK
      CVE: NA
      
      Reference: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f
      
      ----------------------------------------
      
      Kmemleak reported the following leak info in try_smi_init():
      
      unreferenced object 0xffff00018ecf9400 (size 1024):
        comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s)
        backtrace:
          [<000000004ca5b312>] __kmalloc+0x4b8/0x7b0
          [<00000000953b1072>] try_smi_init+0x148/0x5dc [ipmi_si]
          [<000000006460d325>] 0xffff800081b10148
          [<0000000039206ea5>] do_one_initcall+0x64/0x2a4
          [<00000000601399ce>] do_init_module+0x50/0x300
          [<000000003c12ba3c>] load_module+0x7a8/0x9e0
          [<00000000c246fffe>] __se_sys_init_module+0x104/0x180
          [<00000000eea99093>] __arm64_sys_init_module+0x24/0x30
          [<0000000021b1ef87>] el0_svc_common.constprop.0+0x94/0x250
          [<0000000070f4f8b7>] do_el0_svc+0x48/0xe0
          [<000000005a05337f>] el0_svc+0x24/0x3c
          [<000000005eb248d6>] el0_sync_handler+0x160/0x164
          [<0000000030a59039>] el0_sync+0x160/0x180
      
      The problem was that when an error occurred before handlers registration
      and after allocating `new_smi->si_sm`, the variable wouldn't be freed in
      the error handling afterwards since `shutdown_smi()` hadn't been
      registered yet. Fix it by adding a `kfree()` in the error handling path
      in `try_smi_init()`.
      
      Cc: stable@vger.kernel.org # 4.19+
      Fixes: 7960f18a ("ipmi_si: Convert over to a shutdown handler")
      Signed-off-by: NYi Yang <yiyang13@huawei.com>
      Co-developed-by: NGONG, Ruiqi <gongruiqi@huaweicloud.com>
      Signed-off-by: NGONG, Ruiqi <gongruiqi@huaweicloud.com>
      Message-Id: <20230629123328.2402075-1-gongruiqi@huaweicloud.com>
      Signed-off-by: NCorey Minyard <minyard@acm.org>
      
      conflict:
      	drivers/char/ipmi/ipmi_si_intf.c
      Signed-off-by: NYi Yang <yiyang13@huawei.com>
      Reviewed-by: NGUO Zihua <guozihua@huawei.com>
      Reviewed-by: NWang Weiyang <wangweiyang2@huawei.com>
      Signed-off-by: NYongqiang Liu <liuyongqiang13@huawei.com>
      18b2bde9
    • E
      net: add vlan_get_protocol_and_depth() helper · b2202edd
      Eric Dumazet 提交于
      mainline inclusion
      from mainline-v6.4-rc2
      commit 4063384e
      category: bugfix
      bugzilla: https://gitee.com/openeuler/kernel/issues/I7IIRH
      CVE: NA
      
      Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4063384ef762cc5946fc7a3f89879e76c6ec51e2
      
      ---------------------------
      
      Before blamed commit, pskb_may_pull() was used instead
      of skb_header_pointer() in __vlan_get_protocol() and friends.
      
      Few callers depended on skb->head being populated with MAC header,
      syzbot caught one of them (skb_mac_gso_segment())
      
      Add vlan_get_protocol_and_depth() to make the intent clearer
      and use it where sensible.
      
      This is a more generic fix than commit e9d3f809
      ("net/af_packet: make sure to pull mac header") which was
      dealing with a similar issue.
      
      kernel BUG at include/linux/skbuff.h:2655 !
      invalid opcode: 0000 [#1] SMP KASAN
      CPU: 0 PID: 1441 Comm: syz-executor199 Not tainted 6.1.24-syzkaller #0
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
      RIP: 0010:__skb_pull include/linux/skbuff.h:2655 [inline]
      RIP: 0010:skb_mac_gso_segment+0x68f/0x6a0 net/core/gro.c:136
      Code: fd 48 8b 5c 24 10 44 89 6b 70 48 c7 c7 c0 ae 0d 86 44 89 e6 e8 a1 91 d0 00 48 c7 c7 00 af 0d 86 48 89 de 31 d2 e8 d1 4a e9 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41
      RSP: 0018:ffffc90001bd7520 EFLAGS: 00010286
      RAX: ffffffff8469736a RBX: ffff88810f31dac0 RCX: ffff888115a18b00
      RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
      RBP: ffffc90001bd75e8 R08: ffffffff84697183 R09: fffff5200037adf9
      R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000012
      R13: 000000000000fee5 R14: 0000000000005865 R15: 000000000000fed7
      FS: 000055555633f300(0000) GS:ffff8881f6a00000(0000) knlGS:0000000000000000
      CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 0000000020000000 CR3: 0000000116fea000 CR4: 00000000003506f0
      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
      Call Trace:
      <TASK>
      [<ffffffff847018dd>] __skb_gso_segment+0x32d/0x4c0 net/core/dev.c:3419
      [<ffffffff8470398a>] skb_gso_segment include/linux/netdevice.h:4819 [inline]
      [<ffffffff8470398a>] validate_xmit_skb+0x3aa/0xee0 net/core/dev.c:3725
      [<ffffffff84707042>] __dev_queue_xmit+0x1332/0x3300 net/core/dev.c:4313
      [<ffffffff851a9ec7>] dev_queue_xmit+0x17/0x20 include/linux/netdevice.h:3029
      [<ffffffff851b4a82>] packet_snd net/packet/af_packet.c:3111 [inline]
      [<ffffffff851b4a82>] packet_sendmsg+0x49d2/0x6470 net/packet/af_packet.c:3142
      [<ffffffff84669a12>] sock_sendmsg_nosec net/socket.c:716 [inline]
      [<ffffffff84669a12>] sock_sendmsg net/socket.c:736 [inline]
      [<ffffffff84669a12>] __sys_sendto+0x472/0x5f0 net/socket.c:2139
      [<ffffffff84669c75>] __do_sys_sendto net/socket.c:2151 [inline]
      [<ffffffff84669c75>] __se_sys_sendto net/socket.c:2147 [inline]
      [<ffffffff84669c75>] __x64_sys_sendto+0xe5/0x100 net/socket.c:2147
      [<ffffffff8551d40f>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
      [<ffffffff8551d40f>] do_syscall_64+0x2f/0x50 arch/x86/entry/common.c:80
      [<ffffffff85600087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
      
      Fixes: 469acedd ("vlan: consolidate VLAN parsing code and limit max parsing depth")
      Reported-by: Nsyzbot <syzkaller@googlegroups.com>
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Cc: Toke Høiland-Jørgensen <toke@redhat.com>
      Cc: Willem de Bruijn <willemb@google.com>
      Reviewed-by: NSimon Horman <simon.horman@corigine.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NLiu Jian <liujian56@huawei.com>
      
      Conflicts:
      	drivers/net/tap.c
      	net/packet/af_packet.c
      Reviewed-by: NYue Haibing <yuehaibing@huawei.com>
      Signed-off-by: NYongqiang Liu <liuyongqiang13@huawei.com>
      b2202edd