From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL for-11.2 0/3] NBD patches through 2026-11-19
Date: Thu, 19 Nov 2026 14:23:10 -0600 [thread overview]
Message-ID: <20261119202330.3853797-5-eblake@redhat.com> (raw)
The following changes since commit 08c9bbb825148dec9669f5184ecf18823bb6d631:
Update version for v11.2.0-rc1 release (2026-11-18 12:57:24 -0800)
are available in the Git repository at:
https://gitlab.com/ebblake/qemu.git tags/pull-nbd-2026-11-19
for you to fetch changes up to 470888ffb0220911a0ab58f9ffd41d95f36e4a22:
nbd/client: Don't leak uninitialized memory on malicious server (2026-11-19 14:21:23 -0600)
----------------------------------------------------------------
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(-)
--
2.56.1
next reply other threads:[~2026-11-19 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 20:23 Eric Blake [this message]
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
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=20261119202330.3853797-5-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@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.