Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Abdifatah Suruur <suruurism@gmail.com>
To: pablo@netfilter.org
Cc: stable@vger.kernel.org, fw@strlen.de, security@kernel.org,
	w@1wt.eu, sashal@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [SECURITY] netfilter: nft_byteorder leaks uninitialised kernel stack on 6.12.y with CONFIG_INIT_STACK_NONE (CWE-457)
Date: Wed, 21 Oct 2026 15:47:44 +0300	[thread overview]
Message-ID: <179258686469.28311.5894488032414438351@gmail.com> (raw)
In-Reply-To: <atXZxmkU9Yrv4h_b@chamomile>

Hi Pablo,

I am not asking for a CVE for the upstream code, and I am not disputing
that bb061d3 fixes it in 7.1. I have not sent a cve@kernel.org request.

The only reason I mentioned a CVE is that 6.12.y still carries the
pre-bb061d3 multi-register path, and with CONFIG_INIT_STACK_NONE the
marked-but-unwritten destination word is exposed to a later nft load.
That is why I sent the 6.12.y backport rather than a mainline patch. On
the default CONFIG_INIT_STACK_ALL_ZERO builds the same oracle reads
zero, so the affected population is narrow.

If you and the CNA consider a stable-only infoleak that is already fixed
upstream not CVE-worthy, I will drop the request. The stable fix is the
part that matters to me. If you do want it tracked, I will follow the
documented process once the patch is queued.

Thanks,
Abdifatah Suruur

  reply	other threads:[~2026-10-21 12:47 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 [this message]
2026-10-23 12:57             ` Greg KH
2026-10-23 14:20               ` Abdifatah Suruur
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=179258686469.28311.5894488032414438351@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