[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210419.153405.1531590596849653615.davem@davemloft.net>
Date: Mon, 19 Apr 2021 15:34:05 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gustavo@...eddedor.com
Cc: patchwork-bot+netdevbpf@...nel.org, gustavoars@...nel.org,
vyasevich@...il.com, nhorman@...driver.com,
marcelo.leitner@...il.com, kuba@...nel.org,
linux-sctp@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH][next] sctp: Fix out-of-bounds warning in
sctp_process_asconf_param()
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
Date: Fri, 16 Apr 2021 19:07:05 -0500
> Dave,
>
> On 4/16/21 19:00, patchwork-bot+netdevbpf@...nel.org wrote:
>> Hello:
>>
>> This patch was applied to netdev/net-next.git (refs/heads/master):
>>
>> On Fri, 16 Apr 2021 14:12:36 -0500 you wrote:
>>> Fix the following out-of-bounds warning:
>>>
>>> net/sctp/sm_make_chunk.c:3150:4: warning: 'memcpy' offset [17, 28] from the object at 'addr' is out of the bounds of referenced subobject 'v4' with type 'struct sockaddr_in' at offset 0 [-Warray-bounds]
>>>
>>> This helps with the ongoing efforts to globally enable -Warray-bounds
>>> and get us closer to being able to tighten the FORTIFY_SOURCE routines
>>> on memcpy().
>>>
>>> [...]
>>
>> Here is the summary with links:
>> - [next] sctp: Fix out-of-bounds warning in sctp_process_asconf_param()
>> https://git.kernel.org/netdev/net-next/c/e5272ad4aab3
>
> Thanks for this. Can you take these other two, as well, please?
>
> https://lore.kernel.org/linux-hardening/20210416201540.GA593906@embeddedor/
> https://lore.kernel.org/linux-hardening/20210416193151.GA591935@embeddedor/
>
Done.
Powered by blists - more mailing lists