Quick answers
- Is CVE-2026-93283 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93283 being exploited in the wild.
- How severe is CVE-2026-93283?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux kernel affected versions prior to patch commit 74be657d98a8d684c0475f3cbd450ef2a30ffc73.
- Is there a fix for CVE-2026-93283?
- A patch was published on 2026-07-02: commit 74be657d98a8d684c0475f3cbd450ef2a30ffc73 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93283 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93283?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
When device_register() fails in i3c_master_register_new_i3c_devs(), put_device() is called but leaves dangling pointers in the descriptor structure that can be dereferenced by subsequent code paths like i3c_master_unregister_i3c_devs(). The fix clears desc->dev->desc before calling put_device() and clears desc->dev afterward to prevent use-after-free.
Affected products
- Linux kernel affected versions prior to patch commit 74be657d98a8d684c0475f3cbd450ef2a30ffc73
Timeline
- 2026-09-24: disclosed
- 2026-07-02: patched: commit 74be657d98a8d684c0475f3cbd450ef2a30ffc73