public inbox for linux-hams@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wang Liang <wangliang74@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, linux-hams@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	yuehaibing@huawei.com, zhangchangzhong@huawei.com
Subject: Re: [PATCH net] netrom: Fix memory leak in nr_sendmsg()
Date: Thu, 04 Dec 2025 10:10:06 +0000	[thread overview]
Message-ID: <176484300630.715175.16155719972689096623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251129041315.1550766-1-wangliang74@huawei.com>

Hello:

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

On Sat, 29 Nov 2025 12:13:15 +0800 you wrote:
> syzbot reported a memory leak [1].
> 
> When function sock_alloc_send_skb() return NULL in nr_output(), the
> original skb is not freed, which was allocated in nr_sendmsg(). Fix this
> by freeing it before return.
> 
> [1]
> BUG: memory leak
> unreferenced object 0xffff888129f35500 (size 240):
>   comm "syz.0.17", pid 6119, jiffies 4294944652
>   hex dump (first 32 bytes):
>     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>     00 00 00 00 00 00 00 00 00 10 52 28 81 88 ff ff  ..........R(....
>   backtrace (crc 1456a3e4):
>     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
>     slab_post_alloc_hook mm/slub.c:4983 [inline]
>     slab_alloc_node mm/slub.c:5288 [inline]
>     kmem_cache_alloc_node_noprof+0x36f/0x5e0 mm/slub.c:5340
>     __alloc_skb+0x203/0x240 net/core/skbuff.c:660
>     alloc_skb include/linux/skbuff.h:1383 [inline]
>     alloc_skb_with_frags+0x69/0x3f0 net/core/skbuff.c:6671
>     sock_alloc_send_pskb+0x379/0x3e0 net/core/sock.c:2965
>     sock_alloc_send_skb include/net/sock.h:1859 [inline]
>     nr_sendmsg+0x287/0x450 net/netrom/af_netrom.c:1105
>     sock_sendmsg_nosec net/socket.c:727 [inline]
>     __sock_sendmsg net/socket.c:742 [inline]
>     sock_write_iter+0x293/0x2a0 net/socket.c:1195
>     new_sync_write fs/read_write.c:593 [inline]
>     vfs_write+0x45d/0x710 fs/read_write.c:686
>     ksys_write+0x143/0x170 fs/read_write.c:738
>     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>     do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94
>     entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> [...]

Here is the summary with links:
  - [net] netrom: Fix memory leak in nr_sendmsg()
    https://git.kernel.org/netdev/net/c/613d12dd794e

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



      reply	other threads:[~2025-12-04 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-29  4:13 [PATCH net] netrom: Fix memory leak in nr_sendmsg() Wang Liang
2025-12-04 10: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=176484300630.715175.16155719972689096623.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wangliang74@huawei.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangchangzhong@huawei.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