From: Guanglei Zhu <zhugl3@xiaopeng.com>
To: amit@kernel.org
Cc: virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
liuc63@xiaopeng.com, stable@vger.kernel.org
Subject: [PATCH] virtio: console: check the control packet size before parsing it
Date: Tue, 3 Nov 2026 16:41:56 +0800 [thread overview]
Message-ID: <20261103084156.426810-1-zhugl3@xiaopeng.com> (raw)
The control queue handler hands whatever the host wrote to the
control queue straight to the parser:
buf->len = min_t(size_t, len, buf->size);
buf->offset = 0;
handle_control_message(vq->vdev, portdev, buf);
handle_control_message() casts the start of the buffer to struct
virtio_console_control and reads the id, event and value fields
without ever looking at buf->len. A control packet shorter than the
structure makes the driver parse whatever bytes were left in the
reused buffer as a control header, and the uninitialized event then
drives the port state machine.
Drop control packets that are too short to hold the header.
Fixes: 17634ba25544 ("virtio: console: Add a new MULTIPORT feature, support for generic ports")
Cc: stable@vger.kernel.org
Signed-off-by: Guanglei Zhu <zhugl3@xiaopeng.com>
---
drivers/char/virtio_console.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index 019bcae81af5..5e2a4403dbf8 100644
--- a/drivers/char/virtio_console.c
+++ b/drivers/char/virtio_console.c
@@ -1597,6 +1597,12 @@ static void handle_control_message(struct virtio_device *vdev,
size_t name_size;
int err;
+ if (buf->len < sizeof(struct virtio_console_control)) {
+ dev_dbg(&portdev->vdev->dev,
+ "Invalid control packet size %zu\n", buf->len);
+ return;
+ }
+
cpkt = (struct virtio_console_control *)(buf->buf + buf->offset);
port = find_port_by_id(portdev, virtio32_to_cpu(vdev, cpkt->id));
--
2.50.1
next reply other threads:[~2026-11-03 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:41 Guanglei Zhu [this message]
2026-11-03 9:39 ` Michael S. Tsirkin
2026-11-03 11:17 ` Guanglei Zhu
2026-11-03 11:33 ` Michael S. Tsirkin
2026-11-03 11:59 ` Guanglei Zhu
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=20261103084156.426810-1-zhugl3@xiaopeng.com \
--to=zhugl3@xiaopeng.com \
--cc=amit@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuc63@xiaopeng.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®