+-- On Thu, 29 Nov 2018, Eric Blake wrote --+ | How important is this for 3.1? We've missed -rc3. Is this CVE quality | because of a guest being able to cause mayhem by intentionally getting into | this condition (in which case, we need it, as well as a CVE assigned)? Is it | pre-existing in 3.0 at which point waiting for 4.0 is no worse off than what | we already are?
It is a revised patch to fix 'CVE-2018-17963' issue. Earlier patch was included in -rc0. $ git tag --contains 1592a9947036d60dde5404204a5d45975133caf5 v3.1.0-rc0 v3.1.0-rc1 v3.1.0-rc2 v3.1.0-rc3 Thank you. -- Prasad J Pandit / Red Hat Product Security Team 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F