From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: yahia <yahia.a.abdrabou@gmail.com>
Cc: W_Armin@gmx.de, platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] wmi/core: fix use-after-free in wmi_add_device()
Date: Fri, 3 Jul 2026 15:28:31 +0300 (EEST) [thread overview]
Message-ID: <2df479ed-7a3d-7f89-9f2c-77d5a8270837@linux.intel.com> (raw)
In-Reply-To: <20260622191838.23187-1-yahia.a.abdrabou@gmail.com>
On Mon, 22 Jun 2026, yahia wrote:
> From: yahia ahmed <yahia.a.abdrabou@gmail.com>
So do I get it right that the conclusion of the discussion was that this
still required?
If that's the case, here's things that need to be fixed:
> Fix a use-after-free error in wmi_add_device()
> where if a device_add() fails, it will forward
> the error code to the caller function parse_wdg(),
> which then frees wblock, but doesn't remove it From
> pdev's list, thus if pdev were to call it, it will
> call freed memory and result in a use-after-free
Please add the final stop (.)
The lines are too short, please reflow the paragraph to 72 characters.
>
> Signed-off-by: yahia ahmed <yahia.a.abdrabou@gmail.com>
A Fixes tag?
> ---
> v3:
> - Fix corruption in v2
> v2:
> - Fix use-after-free in wmi_add_device() by using device_link_del()
> drivers/platform/wmi/core.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/wmi/core.c b/drivers/platform/wmi/core.c
> index 529825dcfbfe..1afc4d12bdfb 100644
> --- a/drivers/platform/wmi/core.c
> +++ b/drivers/platform/wmi/core.c
> @@ -1268,6 +1268,7 @@ static int wmi_create_device(struct device *wmi_bus_dev,
> static int wmi_add_device(struct platform_device *pdev, struct wmi_device *wdev)
> {
> struct device_link *link;
> + int ret;
>
> /*
> * Many aggregate WMI drivers do not use -EPROBE_DEFER when they
> @@ -1282,7 +1283,11 @@ static int wmi_add_device(struct platform_device *pdev, struct wmi_device *wdev)
> if (!link)
> return -EINVAL;
>
> - return device_add(&wdev->dev);
> + ret = device_add(&wdev->dev);
> +
> + if (ret)
Please don't leave empty line between call and its error handling.
> + device_link_del(link);
> + return ret;
> }
>
> /*
>
--
i.
prev parent reply other threads:[~2026-07-03 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 0:02 [PATCH] wmi/core Fix use-after-free in parse_wdg() yahia
2026-06-22 14:45 ` Armin Wolf
2026-06-22 19:04 ` [PATCH v2] wmi/core: fix use-after-free in wmi_add_device() yahia
2026-06-22 19:18 ` [PATCH v3] " yahia
2026-06-22 19:45 ` Armin Wolf
2026-06-22 20:25 ` Re " yahia
2026-06-22 20:45 ` Armin Wolf
2026-06-22 20:57 ` yahia
2026-06-22 21:19 ` Armin Wolf
2026-06-23 0:12 ` yahia
2026-07-01 4:19 ` Armin Wolf
2026-07-01 9:42 ` yahia
2026-07-03 12:28 ` Ilpo Järvinen [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=2df479ed-7a3d-7f89-9f2c-77d5a8270837@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yahia.a.abdrabou@gmail.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