From: Florian Westphal <fw@strlen.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Igor Garofano <igorgarofano@gmail.com>,
security@kernel.org, pablo@netfilter.org,
netfilter-devel@vger.kernel.org
Subject: Re: [SECURITY] nft_byteorder: incorrect u32* stride in 64-bit byteorder eval leading to firewall bypass
Date: Sat, 23 May 2026 16:39:00 +0200 [thread overview]
Message-ID: <ahG8BDd06vVmOTMw@strlen.de> (raw)
In-Reply-To: <2026052028-grain-pencil-0d8b@gregkh>
Greg KH <gregkh@linuxfoundation.org> wrote:
> Can you turn this into a real patch that can be applied so you get full
> credit for resolving this issue?
A patch to remove the buggy loop is queued in nf-next:testing and scheduled
for a pull request on monday.
prev parent reply other threads:[~2026-05-23 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOOOOYyfpwO7inyq2wXtpT0kY0s19-n4OZf2MCR62WRi7vzMMg@mail.gmail.com>
2026-05-19 18:34 ` [SECURITY] nft_byteorder: incorrect u32* stride in 64-bit byteorder eval leading to firewall bypass Florian Westphal
2026-05-20 12:13 ` Greg KH
2026-05-20 12:17 ` Florian Westphal
2026-05-20 12:30 ` Greg KH
2026-05-23 14:39 ` Florian Westphal [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=ahG8BDd06vVmOTMw@strlen.de \
--to=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=igorgarofano@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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.