From: sashiko-bot@kernel.org
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v4 2/4] leds: trigger: netdev: Access net_dev under trigger_data->lock in the worker
Date: Thu, 01 Oct 2026 13:20:29 +0000 [thread overview]
Message-ID: <20261001132029.B90351F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001131206.2513248-3-alexander.sverdlin@siemens.com>
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> netdev_trig_work() dereferences trigger_data->net_dev without the lock,
> while set_device_name() and netdev_trig_notify() dev_put() and replace it
> under trigger_data->lock. On NETDEV_UNREGISTER the worker can run
> dev_get_stats() on a netdev being freed (UAF).
>
> Take trigger_data->lock in the worker. cancel_delayed_work_sync() must
> then never run under that lock.
>
> Cc: stable@vger.kernel.org
> Closes: https://lore.kernel.org/all/20260914142116.6DAC51F000FF@smtp.kernel.org/
> Fixes: 06f502f57d0d ("leds: trigger: Introduce a NETDEV trigger")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001131206.2513248-1-alexander.sverdlin@siemens.com?part=2
next prev parent reply other threads:[~2026-10-01 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:11 [PATCH v4 0/4] leds: trigger: netdev: fix sysfs_update_group() races A. Sverdlin
2026-10-01 13:12 ` [PATCH v4 1/4] leds: trigger: netdev: Put netdev on activate error path A. Sverdlin
2026-10-01 13:22 ` sashiko-bot
2026-10-01 13:12 ` [PATCH v4 2/4] leds: trigger: netdev: Access net_dev under trigger_data->lock in the worker A. Sverdlin
2026-10-01 13:20 ` sashiko-bot [this message]
2026-10-01 13:12 ` [PATCH v4 3/4] leds: trigger: netdev: Fix sysfs_update_group() races A. Sverdlin
2026-10-01 13:22 ` sashiko-bot
2026-10-01 13:12 ` [PATCH v4 4/4] leds: trigger: netdev: Serialize mode/interval stores with trigger lock A. Sverdlin
2026-10-01 13:20 ` sashiko-bot
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=20261001132029.B90351F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.