Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pavitra Jha <jhapavitra98@gmail.com>
Cc: w@1wt.eu, pabeni@redhat.com, horms@kernel.org,
	chandrashekar.devegowda@intel.com, linux-wwan@lists.linux.dev,
	netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v6] net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler
Date: Wed, 06 May 2026 02:20:14 +0000	[thread overview]
Message-ID: <177803401454.2352352.1722198141421516263.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260501110713.145563-1-jhapavitra98@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  1 May 2026 07:07:12 -0400 you wrote:
> t7xx_port_enum_msg_handler() uses the modem-supplied port_count field as
> a loop bound over port_msg->data[] without checking that the message buffer
> contains sufficient data. A modem sending port_count=65535 in a 12-byte
> buffer triggers a slab-out-of-bounds read of up to 262140 bytes.
> 
> Add a sizeof(*port_msg) check before accessing the port message header
> fields to guard against undersized messages.
> 
> [...]

Here is the summary with links:
  - [v6] net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler
    https://git.kernel.org/netdev/net/c/0e7c074cfcd9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2026-05-06  2:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11  8:39 [PATCH] net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler Pavitra Jha
2026-04-14  9:41 ` Paolo Abeni
2026-04-14 13:17   ` Willy Tarreau
2026-04-14 15:31     ` [PATCH v2] " Pavitra Jha
2026-04-14 16:23       ` Willy Tarreau
2026-04-15  8:47         ` [PATCH v3] " Pavitra Jha
2026-04-16 11:32         ` [PATCH v4] " Pavitra Jha
2026-04-21  8:25           ` Paolo Abeni
2026-04-23 15:07             ` [PATCH v5] " Pavitra Jha
2026-04-27 19:03               ` Simon Horman
2026-04-27 19:04               ` Simon Horman
2026-05-01 11:07                 ` [PATCH v6] " Pavitra Jha
2026-05-06  2:20                   ` patchwork-bot+netdevbpf [this message]
2026-04-15 11:09       ` [PATCH v2] " kernel test robot
2026-04-15 13:37       ` kernel test robot

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=177803401454.2352352.1722198141421516263.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chandrashekar.devegowda@intel.com \
    --cc=horms@kernel.org \
    --cc=jhapavitra98@gmail.com \
    --cc=linux-wwan@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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