linux-kernel - Re: [PATCH v3] [BUGFIX] gpio: reject invalid gpio before getting gpio

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] [day] [month] [year] [list]

Message-ID: <CACRpkdb+ZP8ne2-Wkd4F3sovsRN3GtKFnYA9VbHZcCf2sQqvkw@mail.gmail.com>
Date:   Mon, 7 Aug 2017 14:00:55 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Masami Hiramatsu <masami.hiramatsu@...aro.org>,
        Jassi Brar <jaswinder.singh@...aro.org>
Subject: Re: [PATCH v3] [BUGFIX] gpio: reject invalid gpio before getting gpio_desc

On Wed, Aug 2, 2017 at 6:47 AM, Masami Hiramatsu <mhiramat@...nel.org> wrote:

> Check user-given gpio number and reject it before
> calling gpio_to_desc() because gpio_to_desc() is
> for kernel driver and it expects given gpio number
> is valid (means 0 to 511).
> If given number is invalid, gpio_to_desc() calls
> WARN() and dump registers and stack for debug.
> This means user can easily kick WARN() just by
> writing invalid gpio number (e.g. 512) to
> /sys/class/gpio/export.
>
> Fixes: 0e9a5edf5d01 ("gpio: fix deferred probe detection for legacy API")
> Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@...il.com>
> ---
>   Changes in v3:
>    - Remove unneeded empty lines.

Patch applied for fixes.

Yours,
Linus Walleij