[Qemu-devel] [PULL 0/1] 9p fixes for v3.1.0-rc2

Greg Kurz posted 1 patch 5 years, 4 months ago
Test asan passed
Test checkpatch passed
Test docker-quick@centos7 passed
Test docker-mingw@fedora passed
Test docker-clang@ubuntu passed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20181120120326.30879-1-groug@kaod.org
hw/9pfs/9p.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
[Qemu-devel] [PULL 0/1] 9p fixes for v3.1.0-rc2
Posted by Greg Kurz 5 years, 4 months ago
The following changes since commit 3c035a41dca808f096a128fe2b62d849fe638a25:

  Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2018-11-20' into staging (2018-11-20 10:56:57 +0000)

are available in the Git repository at:

  https://github.com/gkurz/qemu.git tags/for-upstream

for you to fetch changes up to 5b3c77aa581ebb215125c84b0742119483571e55:

  9p: take write lock on fid path updates (CVE-2018-19364) (2018-11-20 13:00:35 +0100)

----------------------------------------------------------------
Fixes yet another use-after-free issue that could be triggered by a
misbehaving guest. This is a follow-up to commit:

commit 5b76ef50f62079a2389ba28cacaf6cce68b1a0ed
Author: Greg Kurz <groug@kaod.org>
Date:   Wed Nov 7 01:00:04 2018 +0100

    9p: write lock path in v9fs_co_open2()

----------------------------------------------------------------
Greg Kurz (1):
      9p: take write lock on fid path updates (CVE-2018-19364)

 hw/9pfs/9p.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
-- 
2.17.2


Re: [Qemu-devel] [PULL 0/1] 9p fixes for v3.1.0-rc2
Posted by Peter Maydell 5 years, 4 months ago
On 20 November 2018 at 12:03, Greg Kurz <groug@kaod.org> wrote:
> The following changes since commit 3c035a41dca808f096a128fe2b62d849fe638a25:
>
>   Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2018-11-20' into staging (2018-11-20 10:56:57 +0000)
>
> are available in the Git repository at:
>
>   https://github.com/gkurz/qemu.git tags/for-upstream
>
> for you to fetch changes up to 5b3c77aa581ebb215125c84b0742119483571e55:
>
>   9p: take write lock on fid path updates (CVE-2018-19364) (2018-11-20 13:00:35 +0100)
>
> ----------------------------------------------------------------
> Fixes yet another use-after-free issue that could be triggered by a
> misbehaving guest. This is a follow-up to commit:
>
> commit 5b76ef50f62079a2389ba28cacaf6cce68b1a0ed
> Author: Greg Kurz <groug@kaod.org>
> Date:   Wed Nov 7 01:00:04 2018 +0100
>
>     9p: write lock path in v9fs_co_open2()
>
> ----------------------------------------------------------------
> Greg Kurz (1):
>       9p: take write lock on fid path updates (CVE-2018-19364)
>
Applied, thanks.

-- PMM