From: Yun Zhou <yun.zhou@windriver.com>
To: <andi.shyti@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yun.zhou@windriver.com>
Subject: [PATCH] i2c: fix use-after-free in debugfs directory during adapter removal
Date: Wed, 29 Jul 2026 16:58:53 +0800 [thread overview]
Message-ID: <20260729085853.1624451-1-yun.zhou@windriver.com> (raw)
Move debugfs_remove_recursive() after device_unregister() in
i2c_del_adapter() to fix a race condition where a new i2c device probe
can access the adapter's already-freed debugfs dentry.
The race occurs when:
1. i2c_del_adapter() calls debugfs_remove_recursive(adap->debugfs),
freeing the debugfs dentry.
2. Before device_unregister() completes, another thread writes to the
sysfs 'new_device' attribute, triggering i2c_device_probe().
3. i2c_device_probe() calls debugfs_create_dir() with the stale
adapter->debugfs pointer, causing a GPF in start_dirop() when
trying to lock the freed inode.
Reported-by: syzbot+1e3d934ee3cff1ac188b@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=1e3d934ee3cff1ac188b
Fixes: 73febd775bdb ("i2c: create debugfs entry per adapter")
Cc: stable@vger.kernel.org
Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
---
drivers/i2c/i2c-core-base.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index 3ec04787a737..9b0f3c783e9c 100644
--- a/drivers/i2c/i2c-core-base.c
+++ b/drivers/i2c/i2c-core-base.c
@@ -1826,8 +1826,6 @@ void i2c_del_adapter(struct i2c_adapter *adap)
i2c_host_notify_irq_teardown(adap);
- debugfs_remove_recursive(adap->debugfs);
-
/* wait until all references to the device are gone
*
* FIXME: This is old code and should ideally be replaced by an
@@ -1839,6 +1837,8 @@ void i2c_del_adapter(struct i2c_adapter *adap)
device_unregister(&adap->dev);
wait_for_completion(&adap->dev_released);
+ debugfs_remove_recursive(adap->debugfs);
+
/* free bus id */
mutex_lock(&core_lock);
idr_remove(&i2c_adapter_idr, adap->nr);
--
2.43.0
next reply other threads:[~2026-07-29 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:58 Yun Zhou [this message]
2026-07-31 21:55 ` [PATCH] i2c: fix use-after-free in debugfs directory during adapter removal Andi Shyti
2026-08-01 3:49 ` Hillf Danton
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=20260729085853.1624451-1-yun.zhou@windriver.com \
--to=yun.zhou@windriver.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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