VulnerabilityPublished 24 Sep 2026Updated 19 Oct 2026

CVE-2026-93283: Linux kernel · i3c: master: Fix device_register() error path

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in d22ad96f1a0c89e0ba66a2facc7430f0923919e3 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

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.
Patch: Available – fixed in d22ad96f1a0c89e0ba66a2facc7430f0923919e3, a14dbdf471001dd0601b0c491184990c178a199c, 74be657d98a8d684c0475f3cbd450ef2a30ffc73 +11

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=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	Fixed in d22ad96f1a0c89e0ba66a2facc7430f0923919e3 a14dbdf471001dd0601b0c491184990c178a199c 74be657d98a8d684c0475f3cbd450ef2a30ffc73 20a2b6df91fd782ef2ff551febef594d0b46a9a7 7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0 7ef12e1dd06e442eebf370f6e53c41bd056d0f22 6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cf 6.6.157 6.6 6.1.188 5bf498623f8397d45f85f14cd631c5e5a565c2fb 5.15.221 5.10.270 5.5
LinuxLinux	Affected =6.7	Fixed in–

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

Community reviews

Loading reviews…