diff options
| author | Adrian Hunter <adrian.hunter@intel.com> | 2026-07-02 21:36:44 +0300 |
|---|---|---|
| committer | Alexandre Belloni <alexandre.belloni@bootlin.com> | 2026-07-20 18:10:40 +0200 |
| commit | a2714ef178e077c0a5ac5959634349eb970341e7 (patch) | |
| tree | c8c5c27e50881bf0a57b25a830d9e0efd4b93d6d /include/linux/i3c | |
| parent | eeedacd0866eec6e9dad2f082a5b828b895a5ed0 (diff) | |
| download | linux-next-a2714ef178e077c0a5ac5959634349eb970341e7.tar.gz linux-next-a2714ef178e077c0a5ac5959634349eb970341e7.zip | |
i3c: master: Fix device_register() error path
When device_register() fails in i3c_master_register_new_i3c_devs(),
put_device() is called to drop the reference taken by
device_register(). That drops the last reference, so the device's
release callback i3c_device_release() runs and frees the i3c_device.
Two problems follow from that:
i3c_device_release() does WARN_ON(i3cdev->desc), so it warns because
desc->dev->desc still points back at the descriptor. Clear it before
calling put_device().
After put_device() frees the i3c_device, desc->dev is left pointing at
freed memory, so clear desc->dev as well. That prevents, for example,
i3c_master_unregister_i3c_devs() seeing desc->dev as non-NULL and
dereferencing it.
Reported-by: sashiko-bot@kernel.org
Link: https://lore.kernel.org/linux-i3c/20260701203053.8F3971F000E9@smtp.kernel.org/
Fixes: cab63f6488761 ("i3c: Fix potential refcount leak in i3c_master_register_new_i3c_devs")
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
Link: https://patch.msgid.link/20260702183644.60827-1-adrian.hunter@intel.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Diffstat (limited to 'include/linux/i3c')
0 files changed, 0 insertions, 0 deletions
