From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andi Shyti <andi.shyti@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: CVE-2024-39362: i2c: acpi: Unbind mux adapters before delete
Date: Tue, 2 Jul 2024 21:16:07 +0200 [thread overview]
Message-ID: <2024070209-tapping-satchel-a949@gregkh> (raw)
In-Reply-To: <364518a3a279657815b631e85f3177880b42f4f7.camel@suse.de>
On Tue, Jul 02, 2024 at 07:05:19PM +0200, Jean Delvare wrote:
> Hi all,
>
> On Tue, 2024-06-25 at 16:22 +0200, Greg Kroah-Hartman wrote:
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > i2c: acpi: Unbind mux adapters before delete
> > (...)
> >
> > The Linux kernel CVE team has assigned CVE-2024-39362 to this issue.
>
> I would like to dispute this CVE. I don't quite understand how this bug
> qualifies as a security bug, considering that only root can load and
> unload overlay SSDT tables. The bug can't be triggered on purpose by a
> remote or local unprivileged user.
>
> The bug causes a warning to be dumped to the kernel log, due to trying
> to unbind a companion device which is already unbound, but as far as I
> can see, that's all. acpi_unbind_one() is a best-effort function, it
> returns 0 no matter what. kernfs_remove_by_ame_ns() will gracefully
> return an error code. I can't see any obvious use-after-free happening
> so I see no way an attacker could exploit this bug.
>
> So I would cancel this CVE.
Now rejected, thanks for the information.
thanks,
greg k-h
prev parent reply other threads:[~2024-07-02 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024062550-CVE-2024-39362-2d27@gregkh>
2024-07-02 17:05 ` CVE-2024-39362: i2c: acpi: Unbind mux adapters before delete Jean Delvare
2024-07-02 19:16 ` Greg Kroah-Hartman [this message]
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=2024070209-tapping-satchel-a949@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Hamish.Martin@alliedtelesis.co.nz \
--cc=andi.shyti@kernel.org \
--cc=cve@kernel.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa+renesas@sang-engineering.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