netdev - Re: [PATCH v2] netlink: do not proceed if dump's start() errs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 30 Sep 2017 07:27:37 +0100 (WEST)
From:   David Miller <davem@...emloft.net>
To:     Jason@...c4.com
Cc:     johannes.berg@...el.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, johannes@...solutions.net
Subject: Re: [PATCH v2] netlink: do not proceed if dump's start() errs

From: "Jason A. Donenfeld" <Jason@...c4.com>
Date: Thu, 28 Sep 2017 00:41:44 +0200

> Drivers that use the start method for netlink dumping rely on dumpit not
> being called if start fails. For example, ila_xlat.c allocates memory
> and assigns it to cb->args[0] in its start() function. It might fail to
> do that and return -ENOMEM instead. However, even when returning an
> error, dumpit will be called, which, in the example above, quickly
> dereferences the memory in cb->args[0], which will OOPS the kernel. This
> is but one example of how this goes wrong.
> 
> Since start() has always been a function with an int return type, it
> therefore makes sense to use it properly, rather than ignoring it. This
> patch thus returns early and does not call dumpit() when start() fails.
> 
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
> Cc: Johannes Berg <johannes@...solutions.net>

Johannes, this looks straightforward to me, but please would you give
it a quick review?

Thank you.