CVE-2026-93283: Linux kernel · i3c: master: Fix device_register() error path
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-93283 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-93283 (opens in a new tab)
- git.kernel.org/stable/c/5bf498623f8397d45f85f14cd631c5e5a565c2fb (opens in a new tab)
- git.kernel.org/stable/c/7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0 (opens in a new tab)
- git.kernel.org/stable/c/6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cf (opens in a new tab)
- git.kernel.org/stable/c/7ef12e1dd06e442eebf370f6e53c41bd056d0f22 (opens in a new tab)
- git.kernel.org/stable/c/d22ad96f1a0c89e0ba66a2facc7430f0923919e3 (opens in a new tab)
- git.kernel.org/stable/c/20a2b6df91fd782ef2ff551febef594d0b46a9a7 (opens in a new tab)
- git.kernel.org/stable/c/a14dbdf471001dd0601b0c491184990c178a199c (opens in a new tab)
- git.kernel.org/stable/c/74be657d98a8d684c0475f3cbd450ef2a30ffc73 (opens in a new tab)
- msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-93283.json (opens in a new tab)
- support.microsoft.com/lifecycle (opens in a new tab)
- first.org/cvss (opens in a new tab)