RE: [PATCH v4 2/5] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

2023-02-01 Thread Tian, Kevin
> From: Jan Beulich > Sent: Wednesday, February 1, 2023 5:30 PM > > On 01.02.2023 06:07, Tian, Kevin wrote: > >> From: Xenia Ragiadakou > >> Sent: Tuesday, January 24, 2023 8:42 PM > >> > >> The variable untrusted_msi indicates whether the system is vulnerable to > >> CVE-2011-1898 due to the

Re: [PATCH v4 2/5] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

2023-02-01 Thread Jan Beulich
On 01.02.2023 06:07, Tian, Kevin wrote: >> From: Xenia Ragiadakou >> Sent: Tuesday, January 24, 2023 8:42 PM >> >> The variable untrusted_msi indicates whether the system is vulnerable to >> CVE-2011-1898 due to the absence of interrupt remapping support. >> Although AMD iommus with interrupt

Re: [PATCH v4 2/5] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

2023-01-31 Thread Xenia Ragiadakou
On 2/1/23 07:07, Tian, Kevin wrote: From: Xenia Ragiadakou Sent: Tuesday, January 24, 2023 8:42 PM The variable untrusted_msi indicates whether the system is vulnerable to CVE-2011-1898 due to the absence of interrupt remapping support. Although AMD iommus with interrupt remapping disabled

RE: [PATCH v4 2/5] x86/iommu: make code addressing CVE-2011-1898 no VT-d specific

2023-01-31 Thread Tian, Kevin
> From: Xenia Ragiadakou > Sent: Tuesday, January 24, 2023 8:42 PM > > The variable untrusted_msi indicates whether the system is vulnerable to > CVE-2011-1898 due to the absence of interrupt remapping support. > Although AMD iommus with interrupt remapping disabled are also affected, > this