From: Guanglei Zhu <zhugl3@xiaopeng.com>
To: netdev@vger.kernel.org
Cc: loic.poulain@oss.qualcomm.com, ryazanov.s.a@gmail.com,
chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v2] net: wwan: t7xx: validate the HS2 message data length
Date: Tue, 29 Sep 2026 10:45:52 +0800 [thread overview]
Message-ID: <20260929024552.249951-1-zhugl3@xiaopeng.com> (raw)
In-Reply-To: <179064985627.31693.17462376426668707461@kernel.org>
Found by manual code inspection of how the t7xx driver validates
modem-supplied lengths: commit 0e7c074cfcd9 ("net: wwan: t7xx:
validate port_count against message length") added this kind of check
for the port enumeration path, but the CTL_ID_HS2_MSG handshake path
was missed. Reachability and impact were then confirmed in a QEMU
guest with a fault injector, as described in the patch notes.
next prev parent reply other threads:[~2026-09-29 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 5:44 [PATCH] net: wwan: t7xx: validate the HS2 message data length Guanglei Zhu
2026-09-09 13:10 ` Loic Poulain
2026-09-10 5:46 ` netdev-bot+sashiko
2026-09-29 2:39 ` [PATCH v2] " Guanglei Zhu
2026-09-29 2:44 ` netdev-bot+sinfo
2026-09-29 2:45 ` Guanglei Zhu [this message]
2026-10-01 17:39 ` netdev-bot+sashiko
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=20260929024552.249951-1-zhugl3@xiaopeng.com \
--to=zhugl3@xiaopeng.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=loic.poulain@oss.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@gmail.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