From: Jakub Kicinski <kuba@kernel.org>
To: memoriaru@foxmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] net: dsa: mxl862xx: bound FDB dump walk with a read limit
Date: Fri, 30 Oct 2026 15:24:32 -0700 [thread overview]
Message-ID: <20261030152432.7a3c9cea@kernel.org> (raw)
In-Reply-To: <tencent_9A3D612B75599BC18E420368621A5A296A05@qq.com>
On Fri, 30 Oct 2026 11:33:12 +0800 memoriaru@foxmail.com wrote:
> How discovered: manual code inspection. We were auditing the
> mxl862xx driver's handling of device-controlled API responses
> (firmware as an untrusted party):
Why are you "auditing mxl862xx driver for handling of device-controlled
API responses"? This is an SoC driver AFAIU, if someone loaded untrusted
FW into the SoC the game is over before it started..
next prev parent reply other threads:[~2026-10-30 22:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261022200434.80182-1-memoriaru@foxmail.com>
2026-10-22 20:04 ` [PATCH net 1/2] net: dsa: mxl862xx: bound FDB dump walk by table capacity memoriaru
2026-10-22 20:07 ` netdev-bot+sinfo
2026-10-22 20:14 ` memoriaru
2026-10-23 20:21 ` netdev-bot+sashiko
2026-10-23 20:32 ` memoriaru
2026-10-22 20:04 ` [PATCH net 2/2] net: dsa: mxl862xx: reject bridge_id 0 from BRIDGE_ALLOC memoriaru
2026-10-23 20:21 ` netdev-bot+sashiko
2026-10-23 20:40 ` [PATCH net v2 0/2] net: dsa: mxl862xx: bound FDB dump walk and validate BRIDGE_ALLOC ids memoriaru
2026-10-23 20:44 ` netdev-bot+sinfo
2026-10-23 21:03 ` memoriaru
2026-10-28 22:44 ` Jakub Kicinski
2026-10-29 11:25 ` [PATCH net v3 " memoriaru
[not found] ` <20261029112528.56652-1-memoriaru@foxmail.com>
2026-10-29 11:25 ` [PATCH net v3 1/2] net: dsa: mxl862xx: bound FDB dump walk with a read limit memoriaru
2026-10-29 11:30 ` netdev-bot+sinfo
2026-10-30 3:33 ` memoriaru
2026-10-30 22:24 ` Jakub Kicinski [this message]
2026-10-30 11:28 ` netdev-bot+sashiko
2026-10-29 11:25 ` [PATCH net v3 2/2] net: dsa: mxl862xx: validate the bridge id returned by BRIDGE_ALLOC memoriaru
2026-10-30 11:28 ` netdev-bot+sashiko
2026-10-31 2:43 ` memoriaru
[not found] <20261023204006.24923-1-memoriaru@foxmail.com>
2026-10-23 20:40 ` [PATCH net v2 1/2] net: dsa: mxl862xx: bound FDB dump walk with a read limit memoriaru
2026-10-23 20:40 ` [PATCH net v2 2/2] net: dsa: mxl862xx: validate the bridge id returned by BRIDGE_ALLOC memoriaru
2026-10-31 8:18 [PATCH net v4 0/3] net: dsa: mxl862xx: bound FDB dump walk and validate BRIDGE_ALLOC ids memoriaru
2026-10-31 8:25 ` netdev-bot+sinfo
2026-10-31 8:41 ` memoriaru
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=20261030152432.7a3c9cea@kernel.org \
--to=kuba@kernel.org \
--cc=memoriaru@foxmail.com \
--cc=netdev@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