From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: CVE-2025-22029: exec: fix the racy usage of fs_struct->in_exec
Date: Wed, 30 Apr 2025 12:57:33 +0200 [thread overview]
Message-ID: <2025043019-cash-amicably-b5e1@gregkh> (raw)
In-Reply-To: <aBH93qMAhgMEGDAY@tiehlicka>
On Wed, Apr 30, 2025 at 12:39:26PM +0200, Michal Hocko wrote:
> Based on a follow up update from Oleg[1] I would like to dispute this
> CVE.
>
> TL;DR version
> : with or without this patch the "if (fs->in_exec)" check in copy_fs()
> : can obviously hit the 1 -> 0 transition.
> :
> : This is harmless, but should be probably fixed just to avoid another report
> : from KCSAN.
What is the link to [1]?
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-30 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025041655-CVE-2025-22029-349f@gregkh>
2025-04-30 10:39 ` Michal Hocko
2025-04-30 10:57 ` Greg Kroah-Hartman [this message]
2025-04-30 11:20 ` Oleg Nesterov
2025-05-01 14:17 ` Greg Kroah-Hartman
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=2025043019-cash-amicably-b5e1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.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
Powered by JetHome