[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210819202825.3545692-1-keescook@chromium.org>
Date: Thu, 19 Aug 2021 13:28:22 -0700
From: Kees Cook <keescook@...omium.org>
To: netdev@...r.kernel.org
Cc: Kees Cook <keescook@...omium.org>,
Stanislav Yakovlev <stas.yakovlev@...il.com>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Jesper Dangaard Brouer <hawk@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
KP Singh <kpsingh@...nel.org>, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-rdma@...r.kernel.org,
bpf@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: [PATCH 0/3] net: Cleanups for FORTIFY_SOURCE
Hi,
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memcpy(), memmove(), and memset(), avoid
intentionally writing across neighboring fields.
These three changes have been living in my memcpy() series[1], but have
no external dependencies. It's probably better to have these go via
netdev.
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/20210818060533.3569517-1-keescook@chromium.org/
Kees Cook (3):
ipw2x00: Avoid field-overflowing memcpy()
net/mlx5e: Avoid field-overflowing memcpy()
pcmcia: ray_cs: Split memcpy() to avoid bounds check warning
drivers/net/ethernet/mellanox/mlx5/core/en.h | 4 +-
.../net/ethernet/mellanox/mlx5/core/en/xdp.c | 4 +-
.../net/wireless/intel/ipw2x00/libipw_rx.c | 56 ++++++-------------
drivers/net/wireless/ray_cs.c | 4 +-
4 files changed, 25 insertions(+), 43 deletions(-)
--
2.30.2
Powered by blists - more mailing lists