From: Hans de Goede <hansg@kernel.org>
To: Yuhao Jiang <danisjiang@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3] ACPI: video: Fix use-after-free in acpi_video_switch_brightness()
Date: Thu, 23 Oct 2025 15:25:27 +0200 [thread overview]
Message-ID: <83852558-0fdc-493c-8f44-95356480c8aa@kernel.org> (raw)
In-Reply-To: <20251022200704.2655507-1-danisjiang@gmail.com>
Hi,
On 22-Oct-25 10:07 PM, Yuhao Jiang wrote:
> The switch_brightness_work delayed work accesses device->brightness
> and device->backlight, which are freed by
> acpi_video_dev_unregister_backlight() during device removal.
>
> If the work executes after acpi_video_bus_unregister_backlight()
> frees these resources, it causes a use-after-free when
> acpi_video_switch_brightness() dereferences device->brightness or
> device->backlight.
>
> Fix this by calling cancel_delayed_work_sync() for each device's
> switch_brightness_work in acpi_video_bus_remove_notify_handler()
> after removing the notify handler that queues the work. This ensures
> the work completes before the memory is freed.
>
> Fixes: 8ab58e8e7e097 ("ACPI / video: Fix backlight taking 2 steps on a brightness up/down keypress")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yuhao Jiang <danisjiang@gmail.com>
> ---
> Changes in v3:
> - Move cancel_delayed_work_sync() to acpi_video_bus_remove_notify_handler()
> instead of acpi_video_bus_unregister_backlight() for better logic placement
> - Link to v2: https://lore.kernel.org/all/20251022042514.2167599-1-danisjiang@gmail.com/
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hansg@kernel.org>
Regards,
Hans
> ---
> drivers/acpi/acpi_video.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/acpi_video.c b/drivers/acpi/acpi_video.c
> index 103f29661576..be8e7e18abca 100644
> --- a/drivers/acpi/acpi_video.c
> +++ b/drivers/acpi/acpi_video.c
> @@ -1959,8 +1959,10 @@ static void acpi_video_bus_remove_notify_handler(struct acpi_video_bus *video)
> struct acpi_video_device *dev;
>
> mutex_lock(&video->device_list_lock);
> - list_for_each_entry(dev, &video->video_device_list, entry)
> + list_for_each_entry(dev, &video->video_device_list, entry) {
> acpi_video_dev_remove_notify_handler(dev);
> + cancel_delayed_work_sync(&dev->switch_brightness_work);
> + }
> mutex_unlock(&video->device_list_lock);
>
> acpi_video_bus_stop_devices(video);
next prev parent reply other threads:[~2025-10-23 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:07 Yuhao Jiang
2025-10-23 13:25 ` Hans de Goede [this message]
2025-10-23 18:51 ` Rafael J. Wysocki
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=83852558-0fdc-493c-8f44-95356480c8aa@kernel.org \
--to=hansg@kernel.org \
--cc=danisjiang@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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®