[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3cb2f39c-b46a-d012-721b-d40285a75aee@gmail.com>
Date: Tue, 15 Feb 2022 13:54:22 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jinmeng Zhou <jjjinmeng.zhou@...il.com>, isdn@...ux-pingi.de,
Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc: netdev@...r.kernel.org, shenwenbosmile@...il.com
Subject: Re: A missing check bug and an inconsistent check bug
On 2/15/22 04:30, Jinmeng Zhou wrote:
> Dear maintainers,
>
> Hi, our tool finds a missing check bug(v4.18.5),
> and an inconsistent check bug (v5.10.7) using static analysis.
> We are looking forward to having more experts' eyes on this. Thank you!
>
> Before calling sk_alloc() with SOCK_RAW type,
> there should be a permission check, ns_capable(ns,CAP_NET_RAW).
>
> In kernel v4.18.5, there is no check in base_sock_create().
> However, v5.10.7 adds a check. (1) So is it a missing check bug?
Same answer, v4.18 is not a stable kernel, not sure why anyone would
care about v4.18.5
Powered by blists - more mailing lists