From: Danish Khateeb <danishkhateeb03@gmail.com>
To: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>
Cc: Andrew Davis <afd@ti.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Danish Khateeb <danishkhateeb03@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH v2] leds: tca6507: Fix use-after-free on unbind
Date: Thu, 15 Oct 2026 09:40:33 -0500 [thread overview]
Message-ID: <20261015144033.56519-1-danishkhateeb03@gmail.com> (raw)
Since the LEDs are registered with devm_led_classdev_register(), they
are unregistered only after tca6507_remove() has cancelled the work.
Unregistering an LED that is on turns it off, which queues the work
again from led_assign(), and the work then runs after devres has freed
the chip:
BUG: KASAN: slab-use-after-free in assign_work+0x414/0x5b0
Read of size 8 at addr ffff888010d5c0c0 by task kworker/1:2/65
...
Last potentially related work creation:
...
queue_work_on+0xb6/0xc0
led_assign+0x223/0x340 [leds_tca6507]
led_classdev_unregister+0x26b/0x340
release_nodes+0xb3/0x140
devres_release_group+0x247/0x470
i2c_device_remove+0xbf/0x1b0
Set up the work with devm_work_autocancel() before the LEDs are
registered, so that devres cancels it after they are gone, and drop
tca6507_remove().
Fixes: 1b5c2fa7081c ("leds: tca6507: Use devm_led_classdev_register() to simplify remove path")
Cc: stable@vger.kernel.org
Acked-by: Andrew Davis <afd@ti.com>
Assisted-by: LLM
Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
---
Notes:
Changes in v2:
- Move the new include to the top of the list, where it sorts
alphabetically (Lee)
- Drop the comment above devm_work_autocancel() (Lee)
- Add Andrew's Acked-by
- Link to v1: https://lore.kernel.org/all/20260926172115.543800-1-danishkhateeb03@gmail.com/
Tested in QEMU on a next-20260925 KASAN kernel, with the driver built as
a module and a test-only module that adds a fake I2C adapter and a
software node for a TCA6507 with two LEDs. With the LEDs on, unbinding
hits the report above (38 reports in 20 unbind/bind cycles), and so does
unloading the driver in 2 of 3 runs. With this patch there are no
reports in 20 cycles or 3 unloads, and the LEDs come back after each
rebind. A W=1 build with GPIOLIB is clean.
v2 was retested the same way on next-20260930: 39 reports in 20 cycles
without the patch, none with it in 20 cycles or 3 unloads.
drivers/leds/leds-tca6507.c | 15 +++++----------
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/leds/leds-tca6507.c b/drivers/leds/leds-tca6507.c
index 9afe2722986c..0f987e551f03 100644
--- a/drivers/leds/leds-tca6507.c
+++ b/drivers/leds/leds-tca6507.c
@@ -71,6 +71,7 @@
* not recognised when matching.
*/
+#include <linux/devm-helpers.h>
#include <linux/module.h>
#include <linux/slab.h>
#include <linux/leds.h>
@@ -735,9 +736,11 @@ static int tca6507_probe(struct i2c_client *client)
return -ENOMEM;
tca->client = client;
- INIT_WORK(&tca->work, tca6507_work);
spin_lock_init(&tca->lock);
- i2c_set_clientdata(client, tca);
+
+ err = devm_work_autocancel(dev, &tca->work, tca6507_work);
+ if (err)
+ return err;
for (i = 0; i < NUM_LEDS; i++) {
struct tca6507_led *l = tca->leds + i;
@@ -766,20 +769,12 @@ static int tca6507_probe(struct i2c_client *client)
return 0;
}
-static void tca6507_remove(struct i2c_client *client)
-{
- struct tca6507_chip *tca = i2c_get_clientdata(client);
-
- cancel_work_sync(&tca->work);
-}
-
static struct i2c_driver tca6507_driver = {
.driver = {
.name = "leds-tca6507",
.of_match_table = of_match_ptr(of_tca6507_leds_match),
},
.probe = tca6507_probe,
- .remove = tca6507_remove,
.id_table = tca6507_id,
};
base-commit: 05b4738b0078f7d6f154f68068a11c8a0635e9df
--
2.56.0
reply other threads:[~2026-10-15 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261015144033.56519-1-danishkhateeb03@gmail.com \
--to=danishkhateeb03@gmail.com \
--cc=afd@ti.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@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®