All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH for-11.1 0/3] dmg: add missing input validation (CVE-2026-65929 & CVE-2026-65928)
Date: Fri, 24 Jul 2026 17:15:23 +0200	[thread overview]
Message-ID: <amOBixUuhV1Q6Ica@redhat.com> (raw)
In-Reply-To: <20260723144519.364701-1-stefanha@redhat.com>

Am 23.07.2026 um 16:45 hat Stefan Hajnoczi geschrieben:
> The read-only dmg block driver can crash or leak information when it encounters
> a malicious DMG file. The severity of these issues is low because the block
> driver is used in qemu-img convert workflows where there is no sensitive
> information to leak and crashing is a self-DoS.
> 
> See the individual patches for descriptions of the bugs.

Thanks, applied to the block branch.

Kevin



      parent reply	other threads:[~2026-07-24 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 14:45 [PATCH for-11.1 0/3] dmg: add missing input validation (CVE-2026-65929 & CVE-2026-65928) Stefan Hajnoczi
2026-07-23 14:45 ` [PATCH for-11.1 1/3] dmg: fix out-of-bounds load in search_chunk() (CVE-2026-65929) Stefan Hajnoczi
2026-07-24  6:41   ` Philippe Mathieu-Daudé
2026-07-24 14:27   ` Kevin Wolf
2026-07-23 14:45 ` [PATCH for-11.1 2/3] dmg: refuse to open files with no chunks Stefan Hajnoczi
2026-07-24  6:37   ` Philippe Mathieu-Daudé
2026-07-23 14:45 ` [PATCH for-11.1 3/3] dmg: reject inconsistent UDRW chunk sector count and length (CVE-2026-65928) Stefan Hajnoczi
2026-07-24 15:15 ` Kevin Wolf [this message]

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=amOBixUuhV1Q6Ica@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.