From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1CA5FC433F5 for ; Tue, 11 Oct 2022 06:18:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229691AbiJKGSO (ORCPT ); Tue, 11 Oct 2022 02:18:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41720 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229699AbiJKGSC (ORCPT ); Tue, 11 Oct 2022 02:18:02 -0400 Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5A46F876AF for ; Mon, 10 Oct 2022 23:18:01 -0700 (PDT) Received: by mail-pj1-x1030.google.com with SMTP id n18-20020a17090ade9200b0020b0012097cso915465pjv.0 for ; Mon, 10 Oct 2022 23:18:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=PL23sMexpwn40kFVUCoq7aeOuxcWfa90L83fdjYFkLY=; b=f6DL3dxWhfQZmKFmUHwx772NtYi0pI9Iju4bXuzYcNgU9tZRwWO23ZROjn/BdwYph8 zS5kHOuhegb7qVyT8JCE/zjOjVJQhGat2ZD/xfafy/Nwct8qKjWTUMZrD0uWLayoRBv2 rpvXb5DG+C65jUvr+BcKzqEJk7FpvjtXZEWX0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PL23sMexpwn40kFVUCoq7aeOuxcWfa90L83fdjYFkLY=; b=C20sNZcxkiU5unrN38caRRJFbtV9RD3pVyviUdZAMop0znqRAQEtPR6T1gvGu/0QZG C1mHBugEU8xaNyo91zMwQijIWaDUdI+GEEcrReJOjE1EyDAu/3ZEzwkJGb7aBn+Mo83q 1bq7QzvE+gbBMCE0sPPETr5fI/78qL6IpwWvqorU9p4nsbJEMsm6C2FxkSABX9UxxMRw YUV/icm3CUexExJ1T49zJOGL2J1IWJgOWlaYiuj+uHfwAjapL7+Y9dPyr5lkgQJtAS7Y vCZo0AQPs6dkS/flYUUiiv2KrdDa5OnK902WK7T12RPm740ZdC6EpyIKj+qR4WZ/3jUX YpjQ== X-Gm-Message-State: ACrzQf0JSPOIqivMyMXY63mbi8rAcjNezukmDTnbXtsa5nALIaXkaBlp Ndfe2j7kR+NsmjS5SYOMTUgNxg== X-Google-Smtp-Source: AMsMyM4LISwAIppjAhD1g2j73VCLB7YWcSS9szvYVpDWrK9Gq7TZ7qkMS3VVH6g/Hn7wVmEdsXnrbg== X-Received: by 2002:a17:903:32d2:b0:17f:9224:6e11 with SMTP id i18-20020a17090332d200b0017f92246e11mr23387269plr.116.1665469080745; Mon, 10 Oct 2022 23:18:00 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id c19-20020a621c13000000b00562b811bb42sm7916863pfc.49.2022.10.10.23.17.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Oct 2022 23:17:59 -0700 (PDT) Date: Mon, 10 Oct 2022 23:17:58 -0700 From: Kees Cook To: kernel test robot Cc: lkp@lists.01.org, lkp@intel.com, linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org, "Gustavo A. R. Silva" , Hawkins Jiawei , Johannes Berg , linux-wireless@vger.kernel.org Subject: Re: [fortify] 54d9469bc5: WARNING:at_net/wireless/wext-core.c:#wireless_send_event Message-ID: <202210102312.1CC8197@keescook> References: <202210110943.6f16f1ea-yujie.liu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202210110943.6f16f1ea-yujie.liu@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-hardening@vger.kernel.org On Tue, Oct 11, 2022 at 11:46:21AM +0800, kernel test robot wrote: > commit: 54d9469bc515dc5fcbc20eecbe19cea868b70d68 ("fortify: Add run-time WARN for cross-field memcpy()") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master > [...] > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): > [...] > [ 95.913726][ T36] memcpy: detected field-spanning write (size 16) of single field "&compat_event->pointer" at net/wireless/wext-core.c:623 (size 4) This was fixed with: e3e6e1d16a4c ("wifi: wext: use flex array destination for memcpy()") I expect this will land before -rc1 closes, but Johannes will know more about the schedule. -- Kees Cook From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1577422025514287451==" MIME-Version: 1.0 From: Kees Cook To: lkp@lists.01.org Subject: Re: [fortify] 54d9469bc5: WARNING:at_net/wireless/wext-core.c:#wireless_send_event Date: Mon, 10 Oct 2022 23:17:58 -0700 Message-ID: <202210102312.1CC8197@keescook> In-Reply-To: <202210110943.6f16f1ea-yujie.liu@intel.com> List-Id: --===============1577422025514287451== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Oct 11, 2022 at 11:46:21AM +0800, kernel test robot wrote: > commit: 54d9469bc515dc5fcbc20eecbe19cea868b70d68 ("fortify: Add run-time = WARN for cross-field memcpy()") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master > [...] > caused below changes (please refer to attached dmesg/kmsg for entire log/= backtrace): > [...] > [ 95.913726][ T36] memcpy: detected field-spanning write (size 16) of= single field "&compat_event->pointer" at net/wireless/wext-core.c:623 (siz= e 4) This was fixed with: e3e6e1d16a4c ("wifi: wext: use flex array destination for memcpy()") I expect this will land before -rc1 closes, but Johannes will know more about the schedule. -- = Kees Cook --===============1577422025514287451==--