mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejas Mutalikdesai <tejasmutalikdesai@gmail.com>
To: andi.shyti@kernel.org
Cc: wsa@kernel.org, vladimir_zapolskiy@mentor.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tejas Mutalikdesai <tejasmutalikdesai@gmail.com>,
	syzbot+c0291c8c9aaa473c7721@syzkaller.appspotmail.com
Subject: [PATCH] i2c: core: move idr_remove() in i2c_del_adapter() before device_unregister()
Date: Fri, 19 Jun 2026 00:16:10 +0530	[thread overview]
Message-ID: <20260618184610.6536-1-tejasmutalikdesai@gmail.com> (raw)

There is a race between i2c_del_adapter() and i2c_get_adapter() that
can trigger a "refcount_t: addition on 0; use-after-free" warning.

The sequence is:

  1. i2c_del_adapter() calls device_unregister(), which drops the
     device refcount to zero (the adapter's release callback fires
     and signals dev_released).

  2. The adapter is still in i2c_adapter_idr because idr_remove()
     hasn't been called yet.

  3. A concurrent i2c_get_adapter() calls idr_find() under core_lock
     and finds the adapter.  try_module_get() succeeds because the
     owning module is still MODULE_STATE_LIVE (this is a hot-remove
     path, not a module unload).

  4. get_device() is called on a kobject whose refcount is already
     zero, triggering refcount_warn_saturate() with REFCOUNT_ADD_UAF.

Fixing this by moving the idr_remove() call to before device_unregister().
Once the adapter is removed from the IDR, any concurrent
i2c_get_adapter() will get NULL from idr_find() and return -ENODEV.
Callers that already hold a device reference are unaffected:
wait_for_completion() correctly waits for them to release it via
i2c_put_adapter().

REPRODUCTION AND VALIDATION: Tested by inserting a msleep(500) after wait_for_completion() to widen
the race window, and using a kernel module that spawns two kthreads: one
calling i2c_del_adapter() and another calling i2c_get_adapter()
concurrently while the module remains MODULE_STATE_LIVE.  Without the
fix, the WARNING fires reliably.  With the fix, i2c_get_adapter()
returns NULL and no WARNING is observed.

Reported-by: syzbot+c0291c8c9aaa473c7721@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=c0291c8c9aaa473c7721
Fixes: 611e12ea0f12 ("i2c: core: manage i2c bus device refcount in i2c_[get|put]_adapter")
Signed-off-by: Tejas Mutalikdesai <tejasmutalikdesai@gmail.com>
---
 drivers/i2c/i2c-core-base.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index a2132d70fb36..780ce42fa950 100644
--- a/drivers/i2c/i2c-core-base.c
+++ b/drivers/i2c/i2c-core-base.c
@@ -1801,6 +1801,16 @@ void i2c_del_adapter(struct i2c_adapter *adap)
 
 	debugfs_remove_recursive(adap->debugfs);
 
+	/* Remove from IDR first so that a concurrent i2c_get_adapter() can
+	 * no longer find this adapter.  Without this ordering,
+	 * i2c_get_adapter() can find the adapter via idr_find() and call
+	 * get_device() after device_unregister() has already dropped the
+	 * refcount to zero, triggering a use-after-free warning.
+	 */
+	mutex_lock(&core_lock);
+	idr_remove(&i2c_adapter_idr, adap->nr);
+	mutex_unlock(&core_lock);
+
 	/* wait until all references to the device are gone
 	 *
 	 * FIXME: This is old code and should ideally be replaced by an
@@ -1812,11 +1822,6 @@ void i2c_del_adapter(struct i2c_adapter *adap)
 	device_unregister(&adap->dev);
 	wait_for_completion(&adap->dev_released);
 
-	/* free bus id */
-	mutex_lock(&core_lock);
-	idr_remove(&i2c_adapter_idr, adap->nr);
-	mutex_unlock(&core_lock);
-
 	/* Clear the device structure in case this adapter is ever going to be
 	   added again */
 	memset(&adap->dev, 0, sizeof(adap->dev));
-- 
2.54.0


             reply	other threads:[~2026-06-18 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 18:46 Tejas Mutalikdesai [this message]
2026-06-18 20:52 ` Wolfram Sang
2026-06-19  3:22   ` Tejas MD
2026-06-19  4:19     ` Wolfram Sang

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=20260618184610.6536-1-tejasmutalikdesai@gmail.com \
    --to=tejasmutalikdesai@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+c0291c8c9aaa473c7721@syzkaller.appspotmail.com \
    --cc=vladimir_zapolskiy@mentor.com \
    --cc=wsa@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®