From: Jenny Guanni Qu <qguanni@gmail.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, berrange@redhat.com,
Jenny Guanni Qu <qguanni@gmail.com>
Subject: [PATCH] hw/audio/sb16: validate VMState fields in post_load
Date: Wed, 18 Mar 2026 19:29:18 +0000 [thread overview]
Message-ID: <20260318192918.65481-1-qguanni@gmail.com> (raw)
The SB16 VMState loads in_index and out_data_len as raw INT32
values with no bounds validation. A crafted migration stream or
VM snapshot can set these to values exceeding their respective
buffer sizes (in2_data[10] and out_data[50]), causing heap OOB
write in dsp_write() and heap OOB read in dsp_read().
Add bounds checks in sb16_post_load() to reject invalid values
before they can be used as array indices.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/3326
Reported-by: Jenny Guanni Qu <qguanni@gmail.com>
Signed-off-by: Jenny Guanni Qu <qguanni@gmail.com>
---
hw/audio/sb16.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/hw/audio/sb16.c b/hw/audio/sb16.c
index 1b5e452a29..1838d3ef7b 100644
--- a/hw/audio/sb16.c
+++ b/hw/audio/sb16.c
@@ -1286,6 +1286,13 @@ static int sb16_post_load (void *opaque, int version_id)
{
SB16State *s = opaque;
+
+ if (s->in_index < 0 || s->in_index > (int)sizeof(s->in2_data)) {
+ return -1;
+ }
+ if (s->out_data_len < 0 || s->out_data_len > (int)sizeof(s->out_data)) {
+ return -1;
+ }
if (s->voice) {
audio_be_close_out(s->audio_be, s->voice);
s->voice = NULL;
--
2.34.1
next reply other threads:[~2026-03-18 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 19:29 Jenny Guanni Qu [this message]
2026-03-24 17:05 ` [PATCH] hw/audio/sb16: validate VMState fields in post_load Paolo Bonzini
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=20260318192918.65481-1-qguanni@gmail.com \
--to=qguanni@gmail.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox