LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: ajk@comnets.uni-bremen.de, davem@davemloft.net, kuba@kernel.org,
	linux-hams@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dan.carpenter@oracle.com,
	syzbot+fc8cd9a673d4577fb2e4@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] net: 6pack: fix slab-out-of-bounds in decode_data
Date: Mon, 16 Aug 2021 10:10:05 +0000	[thread overview]
Message-ID: <162910860507.22499.6005898561031397786.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210813151433.22493-1-paskripkin@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri, 13 Aug 2021 18:14:33 +0300 you wrote:
> Syzbot reported slab-out-of bounds write in decode_data().
> The problem was in missing validation checks.
> 
> Syzbot's reproducer generated malicious input, which caused
> decode_data() to be called a lot in sixpack_decode(). Since
> rx_count_cooked is only 400 bytes and noone reported before,
> that 400 bytes is not enough, let's just check if input is malicious
> and complain about buffer overrun.
> 
> [...]

Here is the summary with links:
  - [v2] net: 6pack: fix slab-out-of-bounds in decode_data
    https://git.kernel.org/netdev/net/c/19d1532a1876

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



  parent reply	other threads:[~2021-08-16 10:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 11:28 [PATCH] " Pavel Skripkin
2021-08-13 14:58 ` Dan Carpenter
2021-08-13 15:09   ` Pavel Skripkin
2021-08-13 15:14   ` [PATCH v2] " Pavel Skripkin
2021-08-13 21:09     ` Dan Carpenter
2021-08-13 21:32       ` Pavel Skripkin
2021-08-16 10:10     ` patchwork-bot+netdevbpf [this message]
2021-08-14  0:23   ` [PATCH] " Kevin Dawson
2021-08-14 14:17     ` Pavel Skripkin
2021-08-16  7:13       ` Dan Carpenter

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=162910860507.22499.6005898561031397786.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ajk@comnets.uni-bremen.de \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paskripkin@gmail.com \
    --cc=syzbot+fc8cd9a673d4577fb2e4@syzkaller.appspotmail.com \
    --subject='Re: [PATCH v2] net: 6pack: fix slab-out-of-bounds in decode_data' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).