The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dust Li <dust.li@linux.alibaba.com>
Cc: wintera@linux.ibm.com, wenjia@linux.ibm.com,
	guwen@linux.alibaba.com, pabeni@redhat.com,
	mjambigi@linux.ibm.com, alibuda@linux.alibaba.com,
	sidraya@linux.ibm.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	federico.kirschbaum@xbow.com
Subject: Re: [PATCH net] dibs: loopback: validate offset and size in move_data()
Date: Thu, 09 Jul 2026 11:10:07 +0000	[thread overview]
Message-ID: <178359540740.3416587.11524899532321320638.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707074318.1448662-1-dust.li@linux.alibaba.com>

Hello:

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

On Tue,  7 Jul 2026 15:43:18 +0800 you wrote:
> The loopback move_data() performs a memcpy into the registered DMB
> without checking whether offset + size exceeds the DMB length.  Unlike
> real ISM hardware, which enforces memory region bounds natively, the
> software loopback has no such protection.
> 
> A peer-supplied out-of-bounds offset or oversized write would result in
> an OOB write past the allocated kernel buffer.  Add an explicit bounds
> check before the memcpy to reject such requests with -EINVAL.
> 
> [...]

Here is the summary with links:
  - [net] dibs: loopback: validate offset and size in move_data()
    https://git.kernel.org/netdev/net/c/78237e3c0720

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



      parent reply	other threads:[~2026-07-09 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  7:43 [PATCH net] dibs: loopback: validate offset and size in move_data() Dust Li
2026-07-07 14:31 ` Dust Li
2026-07-07 18:31   ` Andrew Lunn
2026-07-09 10:46     ` Paolo Abeni
2026-07-09 11:10 ` 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=178359540740.3416587.11524899532321320638.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alibuda@linux.alibaba.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=federico.kirschbaum@xbow.com \
    --cc=guwen@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjambigi@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sidraya@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=wenjia@linux.ibm.com \
    --cc=wintera@linux.ibm.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