From: Dave Jiang <dave.jiang@intel.com>
To: Jiale Yao <yaojiale02@163.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
Li Ming <ming.li@zohomail.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] cxl/acpi: Check ACPI companion before use
Date: Mon, 28 Sep 2026 16:50:15 -0700 [thread overview]
Message-ID: <73faab54-a9df-4053-8012-1ee28f0b2330@intel.com> (raw)
In-Reply-To: <20260926071605.3013893-1-yaojiale02@163.com>
On 9/26/26 12:16 AM, Jiale Yao wrote:
> Platform drivers can be forced to match devices outside their ID tables
> through driver_override. cxl_acpi_probe() assumes that every bound device
> has an ACPI companion and dereferences adev->dev.bus without checking the
> result of ACPI_COMPANION(). Force-binding cxl_acpi to a platform device
> without a companion therefore causes a NULL pointer dereference.
>
> This was reproduced by setting the driver override for the pcspkr platform
> device to cxl_acpi and binding it through sysfs:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000280
> #PF: supervisor read access in kernel mode
> RIP: cxl_acpi_probe+0xf4/0x220
> Call Trace:
> platform_probe+0x4d/0x80
> really_probe+0x106/0x370
> device_driver_attach+0x4c/0xa0
> bind_store+0xd0/0x100
>
> Commit 2b3a5dabe89e ("platform/surface: acpi-notify: Check ACPI
> companion before use") fixed the same force-binding issue in another
> platform driver. Check the companion before setting up the CXL root and
> return -ENODEV when it is absent.
>
> Fixes: 7d4b5ca2e2cb ("cxl/acpi: Add downstream port data to cxl_port instances")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jiale Yao <yaojiale02@163.com>
Applied to cxl/next:
371c2ad16242
> ---
>
> Notes:
> Changes in v2:
> - Move the ACPI companion assignment immediately before its NULL check.
> - Reorder local declarations in reverse Christmas tree order.
>
> drivers/cxl/acpi.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> index 3b818adbd38b..fb09a5ff48c1 100644
> --- a/drivers/cxl/acpi.c
> +++ b/drivers/cxl/acpi.c
> @@ -885,13 +885,17 @@ static int pair_cxl_resource(struct device *dev, void *data)
>
> static int cxl_acpi_probe(struct platform_device *pdev)
> {
> - int rc;
> + struct cxl_cfmws_context ctx;
> + struct acpi_device *adev;
> struct resource *cxl_res;
> struct cxl_root *cxl_root;
> struct cxl_port *root_port;
> struct device *host = &pdev->dev;
> - struct acpi_device *adev = ACPI_COMPANION(host);
> - struct cxl_cfmws_context ctx;
> + int rc;
> +
> + adev = ACPI_COMPANION(host);
> + if (!adev)
> + return -ENODEV;
>
> device_lock_set_class(&pdev->dev, &cxl_root_key);
> rc = devm_add_action_or_reset(&pdev->dev, cxl_acpi_lock_reset_class,
prev parent reply other threads:[~2026-09-28 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 7:16 Jiale Yao
2026-09-27 22:50 ` Jonathan Cameron
2026-09-28 23:50 ` Dave Jiang [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=73faab54-a9df-4053-8012-1ee28f0b2330@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=stable@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=yaojiale02@163.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
all inboxes | Powered by JetHome®