All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: SaifAllah benMassaoud <saifmassaoudi18@gmail.com>
Cc: security@kernel.org, netfilter-devel@vger.kernel.org,
	Florian Westphal <fw@strlen.de>
Subject: Re: [SECURITY] netfilter: nft_limit byte-rate bypass via unchecked u64 multiplication
Date: Sun, 11 Oct 2026 23:43:49 +0200	[thread overview]
Message-ID: <aswDFUpZcFr6jYGL@chamomile> (raw)
In-Reply-To: <CADikNYC4P0F7gz4nCxKcJwsAzXEEA-a-8QRu1TE3SUzXvmcuZA@mail.gmail.com>

On Sun, Oct 11, 2026 at 10:27:07PM +0100, SaifAllah benMassaoud wrote:
> The fact that the kernel does not crash does not, by itself, determine
> whether a bug is security-relevant ( I mean that a security vulnerability
> does not have to crash the kernel to be a security issue) .
> 
> My PoC demonstrates that the byte-rate limit can be bypassed due to an
> arithmetic overflow, allowing traffic that should have been rate-limited to
> pass.
> I understand that bytes/week is an unusual configuration.

It is the user itself that configured this esoteric ratelimit...

> However, nftables accepts it, and the issue is that the kernel
> incorrectly enforces the resulting rule. If this configuration is
> not intended to be supported, rejecting it would be a reasonable
> fix.
> My question is whether the security implications of the demonstrated
> rate-limit bypass were evaluated, rather than whether this is a common
> rate-limit configuration.

We are busy handling _real_ issues, please stop the bullshit.

  parent reply	other threads:[~2026-10-11 21:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 17:01 [SECURITY] netfilter: nft_limit byte-rate bypass via unchecked u64 multiplication SaifAllah benMassaoud
2026-10-11  7:34 ` Pablo Neira Ayuso
     [not found]   ` <CADikNYCzQRErYLwDLoUPrDs8dmuBB8z+45yxKAaps7QTCrLXXA@mail.gmail.com>
2026-10-11 16:55     ` Pablo Neira Ayuso
     [not found]       ` <CADikNYBiijxQjptcYf-2+omXj8Mf5PTGVwK-Ho53E7JEe_ehvQ@mail.gmail.com>
2026-10-11 18:23         ` SaifAllah benMassaoud
2026-10-11 19:14           ` Florian Westphal
     [not found]             ` <CADikNYDzCg46TWPk0dAXQF-Yar+FgEegWEzFZvzCp3x7-k_mOg@mail.gmail.com>
     [not found]               ` <CADikNYBZ5MqJWypk5NFYcxYvPKJhKKyJ5iOWN4JTZrUWf1AUAQ@mail.gmail.com>
2026-10-11 21:11                 ` Pablo Neira Ayuso
     [not found]                   ` <CADikNYC4P0F7gz4nCxKcJwsAzXEEA-a-8QRu1TE3SUzXvmcuZA@mail.gmail.com>
2026-10-11 21:43                     ` Pablo Neira Ayuso [this message]
2026-10-11 22:08                       ` Pablo Neira Ayuso

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=aswDFUpZcFr6jYGL@chamomile \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=saifmassaoudi18@gmail.com \
    --cc=security@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.