From: Greg KH <gregkh@linuxfoundation.org>
To: Manas Ghandat <ghandatmanas@gmail.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
herbert@gondor.apana.org.au, rakshitawasthi17@gmail.com,
security@kernel.org, linux-crypto@vger.kernel.org
Subject: Re: Null deref in scatterwalk_pagedone
Date: Mon, 23 Feb 2026 05:14:05 +0100 [thread overview]
Message-ID: <2026022305-handoff-maverick-13c5@gregkh> (raw)
In-Reply-To: <1205234f-6ddd-4369-834c-6415f8fe0265@gmail.com>
On Mon, Feb 23, 2026 at 09:32:17AM +0530, Manas Ghandat wrote:
>
>
> On 2/23/26 01:51, Eric Biggers wrote:
> > What kernel feature are you using that does GCM encryption? E.g.,
> > IPsec, TLS, SMB, ... Is the code in-tree?
>
> I was fuzzing the TLS subsystem when I found the crash. And yes the code is in-tree.
As this seems to be fixed in 6.19, and you don't have a reproducer,
there's not much we can do here, sorry.
If you do end up with a reproducer, can you submit a backported patch to
stable@vger so that we can queue up the fix for the older kernels?
> > Any reason linux-crypto isn't Cc'ed on this thread?
>
> Aah, my bad. Added it to CC.
Note, they didn't get any of the previous context :(
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-23 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e3044be2-1f05-4cfb-99e4-39dc09e4aeb4@gmail.com>
[not found] ` <63fdfca0-5165-4307-ae8e-c25cbed7f8cb@gmail.com>
[not found] ` <20260222202123.GA37806@quark>
2026-02-23 4:02 ` Null deref in scatterwalk_pagedone Manas Ghandat
2026-02-23 4:14 ` Greg KH [this message]
2026-02-23 4:45 ` Eric Biggers
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=2026022305-handoff-maverick-13c5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=ghandatmanas@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=rakshitawasthi17@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox