[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190416085701.GB4209@kroah.com>
Date: Tue, 16 Apr 2019 10:57:01 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Fuqian Huang <huangfq.daxian@...il.com>
Cc: stable@...r.kernel.org,
Subbu Seetharaman <subbu.seetharaman@...adcom.com>,
Ketan Mukadam <ketan.mukadam@...adcom.com>,
Jitendra Bhivare <jitendra.bhivare@...adcom.com>,
"James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4.14] scsi:be2iscsi: Fix a kernel address leakage in
be_main.c
On Tue, Apr 16, 2019 at 03:06:34PM +0800, Fuqian Huang wrote:
> Outputting kernel addresses will reveal the locations of kernel code
> and data. And there is no need to print the address of a global object
> beiscsi_iscsi_transport in beiscsi_module_init.
> This case is similar to CVE-2018-7273[1].
> Just remove the print statement.
>
> [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7273
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@...il.com>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
Powered by blists - more mailing lists