* Re: CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
[not found] <2025022618-CVE-2022-49562-1d2c@gregkh>
@ 2025-03-16 7:29 ` zhangkunbo
2025-03-16 7:38 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: zhangkunbo @ 2025-03-16 7:29 UTC (permalink / raw)
To: gregkh; +Cc: cve, linux-cve-announce, linux-kernel
Hi, it seems the problem reflected by CVE-2022-49545 has been fixed by
2a8859f373b0. I wonder if applying 2a8859f373b0 could solve the problem
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
2025-03-16 7:29 ` CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits zhangkunbo
@ 2025-03-16 7:38 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2025-03-16 7:38 UTC (permalink / raw)
To: zhangkunbo; +Cc: cve, linux-cve-announce, linux-kernel
On Sun, Mar 16, 2025 at 03:29:12PM +0800, zhangkunbo wrote:
> Hi, it seems the problem reflected by CVE-2022-49545 has been fixed by
> 2a8859f373b0. I wonder if applying 2a8859f373b0 could solve the problem
I'm sorry, but I do not understand what you are talking about here. The
CVE-2022-49545 is an ALSA issue, not KVM.
totally confused,
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-03-16 7:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <2025022618-CVE-2022-49562-1d2c@gregkh>
2025-03-16 7:29 ` CVE-2022-49562: KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits zhangkunbo
2025-03-16 7:38 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox