From: Abdifatah Suruur <suruurism@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: pablo@netfilter.org, stable@vger.kernel.org, fw@strlen.de,
security@kernel.org, w@1wt.eu, sashal@kernel.org
Subject: Re: [SECURITY] netfilter: nft_byteorder leaks uninitialised kernel stack on 6.12.y with CONFIG_INIT_STACK_NONE (CWE-457)
Date: Fri, 23 Oct 2026 17:20:26 +0300 [thread overview]
Message-ID: <179276522631.26562.2889534736321613077@gmail.com> (raw)
In-Reply-To: <2026102330-rockslide-brunt-8616@gregkh>
Hi Greg,
Sorry for the confusion. The patch is the 6.12.y backport I sent to
stable@ on 2026-10-19:
Subject: [PATCH 6.12.y] netfilter: nft_byteorder: remove multi-register support
Message-ID: <179239371327.27230.3709565488726931662@gmail.com>
Cc: you, Florian, Pablo, security@, Willy
It is a full backport of bb061d3de4170741 ("netfilter: nft_byteorder:
remove multi-register support") to 6.12.y, where the pre-bb061d3
multi-register path is still present. It was sent after your reply:
"A full backport is always preferred ... Please submit that and we will
be glad to queue it up."
Sasha queued it on 2026-10-21 for 6.12 and 6.18 (queue commits
d9a6f49f787e0de7447462ee9f63de72ca9ec8c6 and
1eed0466672b84e1b50c149b7bd98886670f65a1).
There is no separate request pending: I have not sent anything to
cve@kernel.org. My note to Pablo was only answering his question about
whether a CVE was being requested for an issue already fixed upstream.
I said I would follow the documented process after the stable fix ships,
and would drop the CVE request if the CNA considers it not CVE-worthy.
The stable fix is the part that matters.
No action needed from you; I am just waiting for the next 6.12.y release.
Thanks,
Abdifatah Suruur
suruurism@gmail.com
next prev parent reply other threads:[~2026-10-23 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <179235055956.10524.6485282696272965887@gmail.com>
[not found] ` <atU2brRgmeb6ght2@1wt.eu>
2026-10-18 22:17 ` [SECURITY] netfilter: nft_byteorder leaks uninitialised kernel stack on 6.12.y with CONFIG_INIT_STACK_NONE (CWE-457) Abdifatah Suruur
2026-10-19 5:48 ` Florian Westphal
2026-10-19 6:08 ` Abdifatah Suruur
2026-10-19 6:58 ` Greg KH
2026-10-19 8:50 ` Pablo Neira Ayuso
2026-10-21 12:47 ` Abdifatah Suruur
2026-10-23 12:57 ` Greg KH
2026-10-23 14:20 ` Abdifatah Suruur [this message]
2026-10-22 4:07 ` Abdifatah Suruur
2026-10-19 20:55 ` Sasha Levin
2026-10-19 21:14 ` Florian Westphal
2026-10-21 12:47 ` Abdifatah Suruur
2026-10-22 2:03 ` Sasha Levin
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=179276522631.26562.2889534736321613077@gmail.com \
--to=suruurism@gmail.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=pablo@netfilter.org \
--cc=sashal@kernel.org \
--cc=security@kernel.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox