From: Sudeep Holla <sudeep.holla@arm.com>
To: George Rurikov <grurikov@gmail.com>
Cc: Robert Moore <robert.moore@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"acpica-devel@lists.linux.dev" <acpica-devel@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ACPICA: Fix dereference in acpi_ev_address_space_dispatch()
Date: Tue, 5 Nov 2024 17:11:13 +0000 [thread overview]
Message-ID: <20241105171113.vifd2x2suoebpt3r@bogus> (raw)
In-Reply-To: <20241031173146.1459-1-grurikov@gmail.com>
On Thu, Oct 31, 2024 at 05:31:46PM +0000, George Rurikov wrote:
> * # Be careful, this email looks suspicious; * WARNING! This email has multiple suspicious indicators that suggest it is malicious, please handle links and attachments with extreme care. *
> When support for PCC Opregion was added, validation of field_obj
> was missed.
> Based on the acpi_ev_address_space_dispatch function description,
> field_obj can be NULL, and also when acpi_ev_address_space_dispatch
> is called in the acpi_ex_region_read() NULL is passed as field_obj.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
LGTM, please submit this to ACPICA project as specified in the documentation
if not already done. Otherwise a reference to the merge request there would
be good here.
--
Regards,
Sudeep
prev parent reply other threads:[~2024-11-05 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 17:31 George Rurikov
2024-10-31 19:51 ` Fedor Pchelkin
2024-11-05 17:11 ` Sudeep Holla [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=20241105171113.vifd2x2suoebpt3r@bogus \
--to=sudeep.holla@arm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=grurikov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=robert.moore@intel.com \
--cc=stable@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
all inboxes | Powered by JetHome®