Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Abdifatah Suruur <suruurism@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, Florian Westphal <fw@strlen.de>,
	security@kernel.org, Willy Tarreau <w@1wt.eu>,
	Sasha Levin <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: Thu, 22 Oct 2026 07:07:58 +0300	[thread overview]
Message-ID: <179264207807.19673.10894070663262050870@gmail.com> (raw)
In-Reply-To: <atXZxmkU9Yrv4h_b@chamomile>

Hi Pablo,

Yes.  The CVE would cover the vulnerability in released stable kernels, not
the upstream change itself.  bb061d3de4170741 is the upstream fix, but it was
not backported, and 6.12.y still leaks uninitialised stack words under
CONFIG_INIT_STACK_NONE; SUSE Leap 16 ships that configuration.

Sasha has now queued the full backport for both 6.12 and 6.18 (queue commits
d9a6f49f787e and 1eed0466672b).  I'll send the CVE request to cve@kernel.org
once it appears in a stable release, per the documented process.  Happy to
adjust if you'd prefer a different sequence.

Thanks,
Abdifatah Suruur
suruurism@gmail.com

  parent reply	other threads:[~2026-10-22  4:08 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
2026-10-22  4:07           ` Abdifatah Suruur [this message]
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=179264207807.19673.10894070663262050870@gmail.com \
    --to=suruurism@gmail.com \
    --cc=fw@strlen.de \
    --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