From: Sebastian Josue Alba Vives <sebasjosue84@gmail.com>
To: security@kernel.org
Cc: gregkh@linuxfoundation.org, shuah@kernel.org,
stable@vger.kernel.org,
"Sebastián Alba Vives" <sebasjosue84@gmail.com>
Subject: [SECURITY] usbip: iso_frame_desc OOB memmove via crafted offset/length
Date: Sun, 29 Mar 2026 07:17:36 -0600 [thread overview]
Message-ID: <20260329131810.522006-1-sebasjosue84@gmail.com> (raw)
In-Reply-To: <20260329125437.517980-1-sebasjosue84@gmail.com>
This is a second vulnerability in the USB/IP iso receive path,
independent from the number_of_packets issue in my previous patch.
After usbip_recv_iso() unpacks iso_frame_desc entries from the
network, the offset and actual_length fields are used by
usbip_pad_iso() in memmove without validating against
transfer_buffer_length.
A malicious server can send valid number_of_packets but with
crafted offset values exceeding the buffer, causing OOB memmove
that corrupts kernel heap memory. No authentication required.
The patch adds per-entry validation that offset + actual_length
falls within transfer_buffer_length.
Found through manual source code auditing.
Reported-by: Sebastián Alba Vives <sebasjosue84@gmail.com>
next prev parent reply other threads:[~2026-03-29 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 12:53 [SECURITY] usbip: vhci: heap buffer overflow via crafted number_of_packets in RET_SUBMIT Sebastian Josue Alba Vives
2026-03-29 12:53 ` [PATCH] usbip: vhci: validate number_of_packets in RET_SUBMIT response Sebastian Josue Alba Vives
2026-03-29 13:25 ` Greg KH
2026-03-29 13:17 ` Sebastian Josue Alba Vives [this message]
2026-03-29 13:17 ` [PATCH] usbip: validate iso_frame_desc offset and length in usbip_recv_iso() Sebastian Josue Alba Vives
2026-03-29 13:24 ` [SECURITY] usbip: vhci: heap buffer overflow via crafted number_of_packets in RET_SUBMIT Greg KH
2026-03-29 13:34 ` Sebastián Alba
2026-03-29 13:50 ` Greg KH
2026-03-29 13:53 ` Sebastián Alba
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=20260329131810.522006-1-sebasjosue84@gmail.com \
--to=sebasjosue84@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=security@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox