From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-cve-announce@vger.kernel.org, <cve@kernel.org>,
<linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: CVE-2023-52656: io_uring: drop any code related to SCM_RIGHTS
Date: Fri, 24 May 2024 12:45:31 -0400 [thread overview]
Message-ID: <871q5rqhuc.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <2024051338-CVE-2023-52656-6545@gregkh> (Greg Kroah-Hartman's message of "Mon, 13 May 2024 15:12:39 +0200")
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> io_uring: drop any code related to SCM_RIGHTS
>
> This is dead code after we dropped support for passing io_uring fds
> over SCM_RIGHTS, get rid of it.
>
> The Linux kernel CVE team has assigned CVE-2023-52656 to this issue.
Hello Greg,
[+Jens in Cc]
This is stable material, but doesn't deserve CVE status. There is
nothing exploitable that is fixed here. Instead, this commit is dropping
unreachable code after the removal of a feature, following another CVE
report. Doing the clean up in the original patch would have made the
real security fix harder to review.
The real issue was reported as CVE-2023-52654 and handled by a different
commit.
--
Gabriel Krisman Bertazi
next parent reply other threads:[~2024-05-24 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024051338-CVE-2023-52656-6545@gregkh>
2024-05-24 16:45 ` Gabriel Krisman Bertazi [this message]
2024-05-24 16:57 ` CVE-2023-52656: io_uring: drop any code related to SCM_RIGHTS Jens Axboe
2024-05-25 7:15 ` Greg Kroah-Hartman
[not found] ` <CAFswPa9jR6mKAsCrdmspCARe-evk16s1t0SG9LrRLCze_f6Ydw@mail.gmail.com>
2024-05-25 15:19 ` Greg Kroah-Hartman
2024-05-25 15:28 ` Jens Axboe
2024-05-25 15:37 ` Greg Kroah-Hartman
2024-05-25 18:15 ` Gabriel Krisman Bertazi
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=871q5rqhuc.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.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