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  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:   Wed, 29 Nov 2017 19:19:05 +0100
From:   SF Markus Elfring <>
To:     Greg Kroah-Hartman <>,
Cc:     Joe Perches <>,
        "Guilherme G. Piccoli" <>,
        Jiri Slaby <>,
        LKML <>,
Subject: Re: jsm_tty: Fix a possible null pointer dereference in two functions

>> It's pretty unlikely, but it is an actual defect.
> No it is not, those variables will never be set to NULL,
> so this can never be triggered.  Walk up the call chain.

If the involved software developers are convinced about the validity
of this pointer:

How do you think about to delete the following condition check
instead in the discussed function implementations?

	if (!ch)


Powered by blists - more mailing lists