From: Hillf Danton <hdanton@sina.com>
To: syzbot+227dbc9afd022922d624@syzkaller.appspotmail.com
Cc: Rafael Alejandro Diaz Cruz <rafad900@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
syzkaller-bugs@googlegroups.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH i2c-fixes v1] i2c: core: Fix use-after-free during i2c device removal
Date: Sat, 22 Aug 2026 16:51:53 +0800 [thread overview]
Message-ID: <20260822085155.1409-1-hdanton@sina.com> (raw)
In-Reply-To: <20260822062621.769921-1-rafad900@gmail.com>
#syz test
A race condition between a process calling i2c_device_probe()
and removal of a USB device by another process leading to both
processes calling debugfs_remove() opens up the possibility of
UAF.
Fix it by adding atomic xchg() and replacing &client->debugfs
with null before calling debugfs_remove() such that the
following statement: "if (IS_ERR_OR_NULL(dentry)) return;"
inside of debugfs_remove() executes properly.
Fixes: d06905d68610 ("i2c: add core-managed per-client directory in debugfs")
Reported-by: syzbot+227dbc9afd022922d624@syzkaller.appspotmail.com
Link: https://syzkaller.appspot.com/bug?extid=227dbc9afd022922d624
Signed-off-by: Rafael Alejandro Diaz Cruz <rafad900@gmail.com>
---
drivers/i2c/i2c-core-base.c | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index fb25704219c7..6fe11232f5ee 100644
--- a/drivers/i2c/i2c-core-base.c
+++ b/drivers/i2c/i2c-core-base.c
@@ -586,8 +586,14 @@ static int i2c_device_probe(struct device *dev)
goto err_clear_wakeup_irq;
}
- client->debugfs = debugfs_create_dir(dev_name(&client->dev),
- client->adapter->debugfs);
+ struct dentry *parent = READ_ONCE(client->adapter->debugfs);
+
+ if (!parent) {
+ status = -ENODEV;
+ goto err_clear_wakeup_irq;
+ }
+
+ client->debugfs = debugfs_create_dir(dev_name(&client->dev), parent);
if (driver->probe)
status = driver->probe(client);
@@ -608,7 +614,10 @@ static int i2c_device_probe(struct device *dev)
return 0;
err_release_driver_resources:
- debugfs_remove_recursive(client->debugfs);
+ // debugfs_remove_recursive(client->debugfs);
+ struct dentry *dir = xchg(&client->debugfs, NULL);
+
+ debugfs_remove_recursive(dir);
devres_release_group(&client->dev, client->devres_group_id);
err_clear_wakeup_irq:
dev_pm_clear_wake_irq(&client->dev);
@@ -632,7 +641,9 @@ static void i2c_device_remove(struct device *dev)
driver->remove(client);
}
- debugfs_remove_recursive(client->debugfs);
+ struct dentry *dir = xchg(&client->debugfs, NULL);
+
+ debugfs_remove_recursive(dir);
devres_release_group(&client->dev, client->devres_group_id);
@@ -1818,6 +1829,8 @@ void i2c_del_adapter(struct i2c_adapter *adap)
i2c_acpi_remove_space_handler(adap);
+ struct dentry *dir = xchg(&adap->debugfs, NULL);
+
i2c_deregister_clients(adap);
/* device name is gone after device_unregister */
@@ -1827,7 +1840,7 @@ void i2c_del_adapter(struct i2c_adapter *adap)
i2c_host_notify_irq_teardown(adap);
- debugfs_remove_recursive(adap->debugfs);
+ debugfs_remove_recursive(dir);
/* wait until all references to the device are gone
*
--
2.43.0
next prev parent reply other threads:[~2026-08-22 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 6:26 [PATCH i2c-fixes v1] i2c: core: Fix use-after-free during i2c device removal Rafael Alejandro Diaz Cruz
2026-08-22 8:51 ` Hillf Danton [this message]
2026-08-22 9:25 ` [syzbot] [fs?] [usb?] KASAN: slab-use-after-free Read in lockref_get (2) syzbot
[not found] ` <CALp66yH7QzvGmo+N7BWykYjoaGT-yAezwRv0Pc_ir6qDRTsKvw@mail.gmail.com>
[not found] ` <CALp66yFrutQ2h8SNyBZn04+LMPMnSEtWxW_Dr0vzfoHvEahSsQ@mail.gmail.com>
2026-08-22 19:11 ` syzbot
2026-08-22 19:37 ` [PATCH i2c-fixes v1] i2c: core: Fix use-after-free during i2c device removal Rafael Alejandro Díaz Cruz
2026-08-22 21:03 ` [syzbot] [fs?] [usb?] KASAN: slab-use-after-free Read in lockref_get (2) syzbot
2026-08-22 23:16 ` [PATCH i2c-fixes v1] i2c: core: Fix use-after-free during i2c device removal Rafael Alejandro Díaz Cruz
2026-08-22 23:57 ` [syzbot] [fs?] [usb?] KASAN: slab-use-after-free Read in lockref_get (2) syzbot
2026-08-23 1:12 ` [PATCH i2c-fixes v1] i2c: core: Fix use-after-free during i2c device removal Rafael Alejandro Díaz Cruz
2026-08-23 3:48 ` [syzbot] [fs?] [usb?] KASAN: slab-use-after-free Read in lockref_get (2) syzbot
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=20260822085155.1409-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafad900@gmail.com \
--cc=syzbot+227dbc9afd022922d624@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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