CVE-2026-93283

Unknown

Last modified

CVE-2026-93283 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1832ed55df45f4145335ad992fb83813cdc58b5d, < 5bf498623f8397d45f85f14cd631c5e5a565c2fb; >= d48fe8d98171e0fffdeaa8b37ce0a6444bff819b, < 20a2b6df91fd782ef2ff551febef594d0b46a9a7; >= 174ae0a3b89e7804e4ea3d31bd83d6e43f39568c, < a14dbdf471001dd0601b0c491184990c178a199c; >= e49a51a96b531f1b4bcd8d358e645b6c74ef67e6, < d22ad96f1a0c89e0ba66a2facc7430f0923919e3; >= cab63f64887616e3c4e31cfd8103320be6ebc8d3, < 7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0; >= cab63f64887616e3c4e31cfd8103320be6ebc8d3, < 7ef12e1dd06e442eebf370f6e53c41bd056d0f22; >= cab63f64887616e3c4e31cfd8103320be6ebc8d3, < 6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cf; >= cab63f64887616e3c4e31cfd8103320be6ebc8d3, < 74be657d98a8d684c0475f3cbd450ef2a30ffc73; 204beeb509d37669de34560e83bb8abffe7ee63a; b24cf43d9babf1265a2bb0ae8d198267cef43b83; >= 5.10.201, < 5.10.270; >= 5.15.139, < 5.15.221; >= 6.1.63, < 6.1.188; >= 6.6.2, < 6.6.157; >= 5.4.261, < 5.5; >= 6.5.12, < 6.6
LinuxLinux6.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93283?
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.
How severe is CVE-2026-93283?
Severity scoring for CVE-2026-93283 is pending analysis.
How do I fix CVE-2026-93283?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93283?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST