From: zhangkunbo <zhangkunbo@huawei.com>
To: <gregkh@linuxfoundation.org>
Cc: <cve@kernel.org>, <linux-cve-announce@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
Date: Sun, 16 Mar 2025 15:29:12 +0800 [thread overview]
Message-ID: <ae0422b3-61a7-4d2c-ab3c-de2d98a9d661@huawei.com> (raw)
In-Reply-To: <2025022618-CVE-2022-49562-1d2c@gregkh>
Hi, it seems the problem reflected by CVE-2022-49545 has been fixed by
2a8859f373b0. I wonder if applying 2a8859f373b0 could solve the problem
next parent reply other threads:[~2025-03-16 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025022618-CVE-2022-49562-1d2c@gregkh>
2025-03-16 7:29 ` zhangkunbo [this message]
2025-03-16 7:38 ` CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits 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=ae0422b3-61a7-4d2c-ab3c-de2d98a9d661@huawei.com \
--to=zhangkunbo@huawei.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox