All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: stable@vger.kernel.org, Florian Westphal <fw@strlen.de>,
	security@kernel.org, Willy Tarreau <w@1wt.eu>
Subject: Re: [SECURITY] netfilter: nft_byteorder leaks uninitialised kernel stack on 6.12.y with CONFIG_INIT_STACK_NONE (CWE-457)
Date: Mon, 19 Oct 2026 10:50:14 +0200	[thread overview]
Message-ID: <atXZxmkU9Yrv4h_b@chamomile> (raw)
In-Reply-To: <179239012164.14465.16534329674629579851@gmail.com>

On Mon, Oct 19, 2026 at 09:08:41AM +0300, Abdifatah Suruur wrote:
> Hi Florian, stable,
> 
> Thanks for the explanation and the Ack.  The explicit memset patch is
> attached with your Acked-by; it applies cleanly to 6.12.113.
> 
> Stable maintainers: would you prefer this minimal init patch or a backport
> of bb061d3de4170741?  Either works from my side.  The memset preserves the
> existing multi-register ABI and is the smaller change; Florian is fine with
> either.
> 
> I will request a CVE via cve@kernel.org once this is queued, per the
> documented process.

Are you requesting a CVE for something that is fixed upstream?

  parent reply	other threads:[~2026-10-19  8:50 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 [this message]
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
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=atXZxmkU9Yrv4h_b@chamomile \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=security@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=suruurism@gmail.com \
    --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 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.