From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] USB serial fixes for 7.2-rc2
Date: Fri, 3 Jul 2026 10:51:33 +0200 [thread overview]
Message-ID: <akd4FQzHuMKG7qQ1@hovoldconsulting.com> (raw)
The following changes since commit ab9de95c9cf952332ab79453b4b5d1bfca8e514f:
Merge tag 'rust-7.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux (2026-06-24 15:11:08 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-7.2-rc2
for you to fetch changes up to 6bfc8d01ac4068eced509f8fc74d0cd205e4dcec:
USB: serial: keyspan_pda: fix information leak (2026-06-30 10:36:06 +0200)
----------------------------------------------------------------
USB serial fixes for 7.2-rc2
Here is a fix for an information leak in the keyspan_pda driver and
three fixes for digi_acceleport addressing stuck rx if a port is closed
while throttled, a hard lockup on disconnect and write buffer
corruption.
Included are also some new modem device ids.
All have been in linux-next for a few days with no reported issues.
----------------------------------------------------------------
Fabio Porcedda (1):
USB: serial: option: add Telit Cinterion FE990D50 compositions
Johan Hovold (4):
USB: serial: digi_acceleport: fix write buffer corruption
USB: serial: digi_acceleport: fix hard lockup on disconnect
USB: serial: digi_acceleport: fix broken rx after throttle
USB: serial: keyspan_pda: fix information leak
drivers/usb/serial/digi_acceleport.c | 43 +++++++++++++++++++++++++++---------
drivers/usb/serial/keyspan_pda.c | 2 +-
drivers/usb/serial/option.c | 16 ++++++++++++++
3 files changed, 50 insertions(+), 11 deletions(-)
next reply other threads:[~2026-07-03 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 8:51 Johan Hovold [this message]
2026-07-03 9:41 ` [GIT PULL] USB serial fixes for 7.2-rc2 Greg Kroah-Hartman
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=akd4FQzHuMKG7qQ1@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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