[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171983823024.2563.3703181588792436256.git-patchwork-notify@kernel.org>
Date: Mon, 01 Jul 2024 12:50:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Heng Qi <hengqi@...ux.alibaba.com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, edumazet@...gle.com,
davem@...emloft.net, pabeni@...hat.com, vladimir.oltean@....com,
jiri@...nulli.us, horms@...nel.org,
syzbot+e77327e34cdc8c36b7d3@...kaller.appspotmail.com
Subject: Re: [PATCH RESEND net-next] net: ethtool: Fix the panic caused by dev
being null when dumping coalesce
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Fri, 28 Jun 2024 12:40:18 +0800 you wrote:
> syzbot reported a general protection fault caused by a null pointer
> dereference in coalesce_fill_reply(). The issue occurs when req_base->dev
> is null, leading to an invalid memory access.
>
> This panic occurs if dumping coalesce when no device name is specified.
>
> Fixes: f750dfe825b9 ("ethtool: provide customized dim profile management")
> Reported-by: syzbot+e77327e34cdc8c36b7d3@...kaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=e77327e34cdc8c36b7d3
> Signed-off-by: Heng Qi <hengqi@...ux.alibaba.com>
>
> [...]
Here is the summary with links:
- [RESEND,net-next] net: ethtool: Fix the panic caused by dev being null when dumping coalesce
https://git.kernel.org/netdev/net-next/c/74d6529b78f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists