All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aamir Ahmed <elb12345@hotmail.co.uk>
Cc: cai.huoqing@linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	kuba@kernel.org
Subject: Re: [PATCH] net: hinic: fix mailbox segment buffer overflow
Date: Thu, 10 Sep 2026 10:50:03 +0000	[thread overview]
Message-ID: <178903740339.1353310.14983402122262555236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AS8P251MB0001AE870B09020B46B5D7DBC8B22@AS8P251MB0001.EURP251.PROD.OUTLOOK.COM>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon,  7 Sep 2026 02:42:34 +0000 you wrote:
> check_mbox_seq_id_and_seg_len() validates that seq_id does not
> exceed SEQ_ID_MAX_VAL (42) and seg_len does not exceed
> MBOX_SEG_LEN (48).  However, this allows the last segment
> (seq_id=42) to carry a full 48-byte payload, writing to offset
> 42*48=2016 for 48 bytes (ending at byte 2064).  The receive
> buffer is only MBOX_MAX_BUF_SZ (2048) bytes, resulting in a
> 16-byte heap buffer overflow.
> 
> [...]

Here is the summary with links:
  - net: hinic: fix mailbox segment buffer overflow
    https://git.kernel.org/netdev/net/c/5d4d98595743

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



      reply	other threads:[~2026-09-10 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  2:42 [PATCH] net: hinic: fix mailbox segment buffer overflow Aamir Ahmed
2026-09-10 10:50 ` patchwork-bot+netdevbpf [this message]

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=178903740339.1353310.14983402122262555236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cai.huoqing@linux.dev \
    --cc=davem@davemloft.net \
    --cc=elb12345@hotmail.co.uk \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.