From: Leon Romanovsky <leon@kernel.org>
To: Lin Ma <linma@zju.edu.cn>, kuba@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
ast@kernel.org, martin.lau@kernel.org, yhs@fb.com,
void@manifault.com, andrii@kernel.org, houtao1@huawei.com,
inwardvessel@gmail.com, kuniyu@amazon.com, songliubraving@fb.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v2] bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
Date: Tue, 25 Jul 2023 07:44:09 +0300 [thread overview]
Message-ID: <20230725044409.GF11388@unreal> (raw)
In-Reply-To: <20230725023330.422856-1-linma@zju.edu.cn>
On Tue, Jul 25, 2023 at 10:33:30AM +0800, Lin Ma wrote:
> The nla_for_each_nested parsing in function bpf_sk_storage_diag_alloc
> does not check the length of the nested attribute. This can lead to an
> out-of-attribute read and allow a malformed nlattr (e.g., length 0) to
> be viewed as a 4 byte integer.
>
> This patch adds an additional check when the nlattr is getting counted.
> This makes sure the latter nla_get_u32 can access the attributes with
> the correct length.
>
> Fixes: 1ed4d92458a9 ("bpf: INET_DIAG support in bpf_sk_storage")
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Lin Ma <linma@zju.edu.cn>
> ---
> V1 -> V2: moves the check to the counting loop as Jakub suggested,
> alters the commit message accordingly.
>
> net/core/bpf_sk_storage.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/net/core/bpf_sk_storage.c b/net/core/bpf_sk_storage.c
> index d4172534dfa8..cca7594be92e 100644
> --- a/net/core/bpf_sk_storage.c
> +++ b/net/core/bpf_sk_storage.c
> @@ -496,8 +496,11 @@ bpf_sk_storage_diag_alloc(const struct nlattr *nla_stgs)
> return ERR_PTR(-EPERM);
>
> nla_for_each_nested(nla, nla_stgs, rem) {
> - if (nla_type(nla) == SK_DIAG_BPF_STORAGE_REQ_MAP_FD)
> + if (nla_type(nla) == SK_DIAG_BPF_STORAGE_REQ_MAP_FD) {
> + if (nla_len(nla) != sizeof(u32))
Jakub, it seems like Lin adds this check to all nla_for_each_nested() loops.
IMHO, the better change will be to change nla_for_each_nested() skip empty/not valid NLAs.
Thanks
> + return ERR_PTR(-EINVAL);
> nr_maps++;
> + }
> }
>
> diag = kzalloc(struct_size(diag, maps, nr_maps), GFP_KERNEL);
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2023-07-25 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 2:33 [PATCH v2] bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing Lin Ma
2023-07-25 4:44 ` Leon Romanovsky [this message]
2023-07-25 5:24 ` Lin Ma
2023-07-25 5:54 ` Leon Romanovsky
2023-07-25 6:05 ` Lin Ma
2023-07-26 3:11 ` Jakub Kicinski
2023-07-27 7:34 ` Paolo Abeni
2023-07-28 23:57 ` Martin KaFai Lau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230725044409.GF11388@unreal \
--to=leon@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=houtao1@huawei.com \
--cc=inwardvessel@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=void@manifault.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).