All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anton Moryakov <ant.v.moryakov@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH V2 iproute2-next] ip: ipmaddr.c: Fix possible integer underflow in read_igmp()
Date: Tue, 29 Jul 2025 23:30:10 +0000	[thread overview]
Message-ID: <175383181025.1684209.1251405483737540810.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250720153843.62145-1-ant.v.moryakov@gmail.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Sun, 20 Jul 2025 18:38:43 +0300 you wrote:
> Static analyzer pointed out a potential error:
> 
> 	Possible integer underflow: left operand is tainted. An integer underflow
> 	may occur due to arithmetic operation (unsigned subtraction) between variable
> 	'len' and value '1', when 'len' is tainted { [0, 18446744073709551615] }
> 
> The fix adds a check for 'len == 0' before accessing the last character of
> the name, and skips the current line in such cases to avoid the underflow.
> 
> [...]

Here is the summary with links:
  - [V2,iproute2-next] ip: ipmaddr.c: Fix possible integer underflow in read_igmp()
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=5734dc8aa703

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



      reply	other threads:[~2025-07-29 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-20 15:38 [PATCH V2 iproute2-next] ip: ipmaddr.c: Fix possible integer underflow in read_igmp() Anton Moryakov
2025-07-29 23:30 ` 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=175383181025.1684209.1251405483737540810.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ant.v.moryakov@gmail.com \
    --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.