From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] lib: add input validation for time, rate, and size parsing functions
Date: Thu, 30 Apr 2026 15:50:08 +0000 [thread overview]
Message-ID: <177756420804.3067548.8196377441992514360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260421202359.632074-1-stephen@networkplumber.org>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 21 Apr 2026 13:23:59 -0700 you wrote:
> The parsing functions get_time(), get_time64(), get_rate(), get_rate64(),
> and get_size64() use strtod() to convert user input but don't validate
> the parsed values. This allows negative numbers and overflow values to
> be passed through, which can cause unexpected behavior or security issues
> when these values reach the kernel as unsigned integers.
>
> Add validation to reject:
> - Negative values (which make no sense for time, rate, or size)
> - Overflow conditions (when strtod() returns HUGE_VAL with ERANGE)
> - Empty strings (already checked, but now with explicit comments)
>
> [...]
Here is the summary with links:
- [iproute2] lib: add input validation for time, rate, and size parsing functions
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=c99a85a7c8eb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-30 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 20:23 [PATCH iproute2] lib: add input validation for time, rate, and size parsing functions Stephen Hemminger
2026-04-30 15:50 ` 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=177756420804.3067548.8196377441992514360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.