netdev - Re: [PATCH] USB: hso: Fix OOB memory access in hso_probe/hso_get_config_data,Re: [PATCH] USB: hso: Fix OOB memory access in hso_probe/hso_get_config

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:   Sun, 09 Dec 2018 12:06:21 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     mathias.payer@...elwelt.net
Cc:     gregkh@...uxfoundation.org, netdev@...r.kernel.org,
        linux-usb@...r.kernel.org, bigeasy@...utronix.de,
        benquike@...il.com
Subject: Re: [PATCH] USB: hso: Fix OOB memory access in
 hso_probe/hso_get_config_data,Re: [PATCH] USB: hso: Fix OOB memory access
 in hso_probe/hso_get_config_data

From: Mathias Payer <mathias.payer@...elwelt.net>
Date: Sun, 9 Dec 2018 21:02:25 +0100

> Passing an int to the macro results in a compiler warning. One option would be
> to test for the individual errors (instead of using the macro) with the drawback
> that future extensions that return different errors may be missed. Another
> alternative is to test for negative values with the drawback that this bypasses
> the existing test macros.

The whole kernel is full of situations where an int is returned and if it's
negative it's an error.  Why is this location so different?

Just check < 0 and be done with it.