All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, QEMU Stable <qemu-stable@nongnu.org>
Subject: Re: [PULL for-11.2 0/3] NBD patches through 2026-11-19
Date: Fri, 20 Nov 2026 12:17:32 -0600	[thread overview]
Message-ID: <awCOZiNf_0DDzecQ@redhat.com> (raw)
In-Reply-To: <4ceec3cf-6903-4cd9-84e3-6522ffc67a1a@tls.msk.ru>

On Fri, Nov 20, 2026 at 11:52:25AM +0300, Michael Tokarev wrote:
> On 11/19/26 23:23, Eric Blake wrote:
> 
> > NBD patches for 2026-11-19
> > 
> > - Eric Blake: CVE-2026-126657: heap leak on client to malicious NBD server
> > 
> > ----------------------------------------------------------------
> > Eric Blake (3):
> >        nbd: Refactor structured payload interpretation
> >        nbd: Pass back offset/length for all structured read replies
> >        nbd/client: Don't leak uninitialized memory on malicious server
> > 
> >   block/nbd.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++----------
> >   1 file changed, 73 insertions(+), 14 deletions(-)
> > 
> 
> Hi Eric!
> 
> This patchset contains a single patch which is marked for-stable, the
> last one.  The first two are not marked as-such.
...

> I'm picking up all 3.  Please let me know if I should not  :)

All three should be backported to stable; the third depends on the
first two being in place. My fault for not applying the tag
consistently, and thanks for double-checking!

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org



      reply	other threads:[~2026-11-20 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 20:23 [PULL for-11.2 0/3] NBD patches through 2026-11-19 Eric Blake
2026-11-19 20:23 ` [PULL 1/3] nbd: Refactor structured payload interpretation Eric Blake
2026-11-19 20:23 ` [PULL 2/3] nbd: Pass back offset/length for all structured read replies Eric Blake
2026-11-19 20:23 ` [PULL 3/3] nbd/client: Don't leak uninitialized memory on malicious server Eric Blake
2026-11-20  0:27 ` [PULL for-11.2 0/3] NBD patches through 2026-11-19 Richard Henderson
2026-11-20  8:52 ` Michael Tokarev
2026-11-20 18:17   ` Eric Blake [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=awCOZiNf_0DDzecQ@redhat.com \
    --to=eblake@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    /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.