public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yilu Lin <linyilu@huawei.com>
Cc: pbonzini@redhat.com, stable@vger.kernel.org,
	"security@kernel.org" <security@kernel.org>,
	caihe <caihe@huawei.com>,
	"Zhangzebin (Zebin, PSIRT)" <zhangzebin@huawei.com>,
	Xiexiangyou <xiexiangyou@huawei.com>,
	xingchaochao <xingchaochao@huawei.com>,
	"lishan (E)" <lishan24@huawei.com>,
	subo7@huawei.com, wanghaibin.wang@huawei.com,
	yuzenghui@huawei.com, xiewenbo@huawei.com
Subject: Re: KVM: a issue which maybe a vulnerability
Date: Mon, 12 Dec 2022 12:57:34 +0100	[thread overview]
Message-ID: <Y5cXLr1E8yypzoo/@kroah.com> (raw)
In-Reply-To: <c77c791d-85b0-b799-8f1e-ec00645e976b@huawei.com>

On Mon, Dec 12, 2022 at 07:15:32PM +0800, Yilu Lin wrote:
> Hello. There is a issue about the kvm module in kernel, which may be a vulnerability. And I need your adivce.
> 
> Here is affect version:
>     Linux kernel version 3.10.The virtualization platform uses the general Linux version before 4.15, which may also involve.
>     The issue is fixed in v4.15-rc1.Commit ID is dedf9c5e216902c6d34b5a0d0c40f4acbb3706d8. Link is https://github.com/torvalds/linux/commit/dedf9c5e216902c6d34b5a0d0c40f4acbb3706d8.
> 

Have you tried backporting this commit to 4.14.y and seeing if it
resolves the issue?  If so, can you send the backport here for
inclusion?

thanks,

greg k-h

      reply	other threads:[~2022-12-12 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1afb632c3c59499bb586d1c5287c92ec@huawei.com>
     [not found] ` <57d8b88a87754e9ab74be19139ea64a7@huawei.com>
     [not found]   ` <Y5BOA69lp1LQ6F1m@kroah.com>
     [not found]     ` <0167aa46-89da-9b91-f1bf-8023ab4b35c7@huawei.com>
     [not found]       ` <Y5btJNMv1nXKLrPE@kroah.com>
     [not found]         ` <743b09f8-3377-7556-2968-0607711b82cb@huawei.com>
2022-12-12 11:15           ` KVM: a issue which maybe a vulnerability Yilu Lin
2022-12-12 11:57             ` Greg KH [this message]

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=Y5cXLr1E8yypzoo/@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=caihe@huawei.com \
    --cc=linyilu@huawei.com \
    --cc=lishan24@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=security@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=subo7@huawei.com \
    --cc=wanghaibin.wang@huawei.com \
    --cc=xiewenbo@huawei.com \
    --cc=xiexiangyou@huawei.com \
    --cc=xingchaochao@huawei.com \
    --cc=yuzenghui@huawei.com \
    --cc=zhangzebin@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox