CVE-2026-93283

i3c: master: Fix device_register() error path

N/A
Published: September 24, 2026 at 03:52 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

174ae0a3b89e7804e4ea3d31bd83d6e43f39568c1832ed55df45f4145335ad992fb83813cdc58b5d204beeb509d37669de34560e83bb8abffe7ee63a5.10.2015.15.1395.4.2616.1.636.5.126.6.26.7b24cf43d9babf1265a2bb0ae8d198267cef43b83cab63f64887616e3c4e31cfd8103320be6ebc8d3d48fe8d98171e0fffdeaa8b37ce0a6444bff819be49a51a96b531f1b4bcd8d358e645b6c74ef67e6
Vendor states this is fixed in 20a2b6df91fd782ef2ff551febef594d0b46a9a7 (fixed)
Vendor states this is fixed in 5bf498623f8397d45f85f14cd631c5e5a565c2fb (fixed)
Vendor states this is fixed in 6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cf (fixed)
Vendor states this is fixed in 74be657d98a8d684c0475f3cbd450ef2a30ffc73 (fixed)
Vendor states this is fixed in 7ef12e1dd06e442eebf370f6e53c41bd056d0f22 (fixed)
Vendor states this is fixed in 7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0 (fixed)
Vendor states this is fixed in a14dbdf471001dd0601b0c491184990c178a199c (fixed)
Vendor states this is fixed in d22ad96f1a0c89e0ba66a2facc7430f0923919e3 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card