All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.14] atm:idt77252: Fix a kernel address leakage in idt77252
Date: Tue, 16 Apr 2019 10:57:20 +0200	[thread overview]
Message-ID: <20190416085720.GC4209@kroah.com> (raw)
In-Reply-To: <20190416071114.13521-1-huangfq.daxian@gmail.com>

On Tue, Apr 16, 2019 at 03:11:14PM +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 
> function idt77252_init in idt77252_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@gmail.com>
> ---
>  drivers/atm/idt77252.c | 2 --
>  1 file changed, 2 deletions(-)

<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>

  reply	other threads:[~2019-04-16  8:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  7:11 [PATCH 4.14] atm:idt77252: Fix a kernel address leakage in idt77252 Fuqian Huang
2019-04-16  8:57 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-18  7:17 Fuqian Huang
2019-04-18  7:42 ` Greg KH
2019-04-16 12:37 Fuqian Huang
2019-04-16 12:46 ` Greg KH
2019-04-16 14:27   ` Fuqian Huang
2019-04-17  6:14     ` Greg KH
2019-04-16 12:31 Fuqian Huang
2019-04-16  6:57 Fuqian Huang
2019-04-16  8:56 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190416085720.GC4209@kroah.com \
    --to=greg@kroah.com \
    --cc=huangfq.daxian@gmail.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.