From: Bjorn Helgaas <helgaas@kernel.org>
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: bhelgaas@google.com, alistair@alistair23.me, jic23@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] PCI/DOE: Fix double free of a duplicate feature's sysfs name
Date: Mon, 5 Oct 2026 18:21:03 -0500 [thread overview]
Message-ID: <20261005232103.GA643044@bhelgaas> (raw)
In-Reply-To: <20261003102221.59894-1-donggeunyoo.kernel@gmail.com>
On Sat, Oct 03, 2026 at 07:22:21PM +0900, Donggeun Yoo wrote:
> When a DOE feature is reported twice, sysfs_add_file_to_group() fails
> with -EEXIST for the second copy and pci_doe_sysfs_feature_populate()
> frees that attribute's name, but leaves the pointer in place.
> pci_doe_sysfs_feature_remove() frees every name again when the device
> is removed, or when a later feature fails to register, so the name is
> freed twice:
>
> BUG: KASAN: double-free in pci_doe_sysfs_feature_remove+0x117/0x1b0
> Call Trace:
> kfree+0x11a/0x420
> pci_doe_sysfs_feature_remove+0x117/0x1b0
> pci_doe_sysfs_teardown+0x90/0xf0
> pci_remove_bus_device+0x128/0x2e0
> pci_stop_and_remove_bus_device_locked+0x1d/0x30
> remove_store+0xd2/0xf0
>
> Clear the pointer after freeing the name.
>
> Fixes: 2311ab1820fe ("PCI/DOE: Expose DOE features via sysfs")
> Cc: stable@vger.kernel.org
> Suggested-by: Alistair Francis <alistair@alistair23.me>
> Assisted-by: LLM
> Signed-off-by: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Applied to pci/doe for v7.4, thanks!
> ---
> Changes in v2:
> - Keep freeing the duplicate's name in pci_doe_sysfs_feature_populate()
> and clear the pointer, instead of leaving it to
> pci_doe_sysfs_feature_remove() (Alistair Francis)
>
> v1: https://lore.kernel.org/all/20260928035035.252394-1-donggeunyoo.kernel@gmail.com/
>
> Tested under QEMU (q35, cxl-type3, KASAN) on 72d3fcf802c4. The device
> reports its CDAT feature once, so a test-only change either registers
> its DOE capability as a second mailbox or inserts the feature N extra
> times into one:
>
> case before after
> no duplicate, remove no report no report
> no duplicate, a name fails at probe no report no report
> two mailboxes, remove double free no report
> two mailboxes, 3 remove/rescan cycles 3 double frees no report
> 3 duplicates in one mailbox, remove 3 double frees no report
> 2 duplicates, a later name fails, 2 double frees no report
> probed twice
>
> The doe_features listing is the same before and after in every case.
>
> drivers/pci/doe.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/doe.c b/drivers/pci/doe.c
> index ac95b1d2d9997..6b5d9ba8e9697 100644
> --- a/drivers/pci/doe.c
> +++ b/drivers/pci/doe.c
> @@ -208,8 +208,9 @@ static int pci_doe_sysfs_feature_populate(struct pci_dev *pdev,
> pci_warn(pdev, "Failed adding %s to sysfs group\n",
> attrs[i].attr.name);
> goto fail;
> - } else
> - kfree(attrs[i].attr.name);
> + }
> + kfree(attrs[i].attr.name);
> + attrs[i].attr.name = NULL;
> }
> }
>
> --
> 2.53.0
>
prev parent reply other threads:[~2026-10-05 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 10:22 Donggeun Yoo
2026-10-04 16:14 ` Jonathan Cameron
2026-10-05 16:20 ` Alistair
2026-10-05 23:21 ` Bjorn Helgaas [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=20261005232103.GA643044@bhelgaas \
--to=helgaas@kernel.org \
--cc=alistair@alistair23.me \
--cc=bhelgaas@google.com \
--cc=donggeunyoo.kernel@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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®