i3c: master: Fix device_register() error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cab63f64887616e3c4e31cfd8103320be6ebc8d3 · < 7ef12e1dd06e442eebf370f6e53c41bd056d0f22| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
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.
From the CVE record · Linux
A failed device_register() call in the Linux kernel's i3c master code can leave a pointer to freed memory, which may later be dereferenced during device unregistration. The input does not specify an attacker action or whether exploitation requires network access, local access, authentication, or user interaction.
Teams running Linux kernels with the affected i3c master code should check their versions; affected versions are not specified.