From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: CVE-2024-35918: randomize_kstack: Improve entropy diffusion
Date: Fri, 26 Jul 2024 11:54:25 +0200 [thread overview]
Message-ID: <2024072606-outlet-stuffy-259b@gregkh> (raw)
In-Reply-To: <lsh7xgorp67fplqey6evmukt66tbstbjob34bwyt7wiklkqu3n@6wftjk4z7xja>
On Fri, Jul 26, 2024 at 11:45:59AM +0200, Michal Koutný wrote:
> Hello.
>
> On Sun, May 19, 2024 at 12:11:12PM GMT, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > randomize_kstack: Improve entropy diffusion
> >
> > The kstack_offset variable was really only ever using the low bits for
> > kernel stack offset entropy. Add a ror32() to increase bit diffusion.
> >
> > The Linux kernel CVE team has assigned CVE-2024-35918 to this issue.
> >
> >
> > Affected and fixed versions
> > ===========================
> >
> > Issue introduced in 5.13 with commit 39218ff4c625 and fixed in 5.15.155 with commit dfb2ce952143
> > Issue introduced in 5.13 with commit 39218ff4c625 and fixed in 6.1.86 with commit e80b4980af26
> > Issue introduced in 5.13 with commit 39218ff4c625 and fixed in 6.6.27 with commit 300a2b9c2b28
> > Issue introduced in 5.13 with commit 39218ff4c625 and fixed in 6.8.6 with commit 6be74b1e21f8
> > Issue introduced in 5.13 with commit 39218ff4c625 and fixed in 6.9 with commit 9c573cd31343
>
> The commit
> 9c573cd313433 ("randomize_kstack: Improve entropy diffusion") v6.9-rc4~35^2
> adds ~2 bits of entropy to stack offsets (+the diffusion, x86_64)
>
> The commit
> 39218ff4c625d ("stack: Optionally randomize kernel stack offset each syscall") v5.13-rc1~184^2~3
> adds ~8 bit of entropy to stack offsets (there was none before, x86_64)
>
> Why the former commit has a CVE while the latter doesn't? (2 < 8)
>
> I'd expect both to be treated equally or even inversely.
If you wish for a CVE to be assigned to 39218ff4c625d, we will be glad
to do so, but it was not on our "old list" of GSD entries to backfill in
CVE entries for, which is why it was not assigned one.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-26 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024051912-CVE-2024-35918-3fed@gregkh>
2024-07-26 9:45 ` CVE-2024-35918: randomize_kstack: Improve entropy diffusion Michal Koutný
2024-07-26 9:54 ` Greg Kroah-Hartman [this message]
2024-07-26 14:12 ` Kees Cook
2024-07-27 7:34 ` Greg Kroah-Hartman
2024-07-29 14:35 ` Michal Koutný
2024-07-30 0:15 ` Kees Cook
2024-07-30 4:56 ` Greg Kroah-Hartman
2024-07-30 9:16 ` Michal Koutný
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=2024072606-outlet-stuffy-259b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
/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