CVE Intelligence
Unknown

CVE-2026-93283 — i3c: master: Fix device_register() error path

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.

Published Sep 24, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.2%
ahead of 9% of scored CVEs · Oct 16, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 204beeb509d37669de34560e83bb8abffe7ee63aversion 6.7≥ 6.5.12 and < 6.6≥ 5.4.261 and < 5.5≥ 6.6.2 and < 6.6.157≥ 6.1.63 and < 6.1.188≥ 5.15.139 and < 5.15.221≥ 5.10.201 and < 5.10.270
and 9 more version b24cf43d9babf1265a2bb0ae8d198267cef43b83≥ 1832ed55df45f4145335ad992fb83813cdc58b5d and < 5bf498623f8397d45f85f14cd631c5e5a565c2fb≥ cab63f64887616e3c4e31cfd8103320be6ebc8d3 and < 74be657d98a8d684c0475f3cbd450ef2a30ffc73≥ cab63f64887616e3c4e31cfd8103320be6ebc8d3 and < 6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cf≥ cab63f64887616e3c4e31cfd8103320be6ebc8d3 and < 7ef12e1dd06e442eebf370f6e53c41bd056d0f22≥ cab63f64887616e3c4e31cfd8103320be6ebc8d3 and < 7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0≥ e49a51a96b531f1b4bcd8d358e645b6c74ef67e6 and < d22ad96f1a0c89e0ba66a2facc7430f0923919e3≥ 174ae0a3b89e7804e4ea3d31bd83d6e43f39568c and < a14dbdf471001dd0601b0c491184990c178a199c≥ d48fe8d98171e0fffdeaa8b37ce0a6444bff819b and < 20a2b6df91fd782ef2ff551febef594d0b46a9a7
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 24, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 3d
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 3d
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93283 is "i3c: master: Fix device_register() error path", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.