Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 20a2b6df91fd782ef2ff551febef594d0b46a9a7, 5.10.270, 5.15.221; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 20a2b6df91fd782ef2ff551febef594d0b46a9a7, 5.10.270, 5.15.221; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93283

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 204beeb509d37669de34560e83bb8abffe7ee63a, b24cf43d9babf1265a2bb0ae8d198267cef43b83, 6.7affected
    • 1832ed55df45f4145335ad992fb83813cdc58b5d and later · before 5bf498623f8397d45f85f14cd631c5e5a565c2fbaffected · git
    • d48fe8d98171e0fffdeaa8b37ce0a6444bff819b and later · before 20a2b6df91fd782ef2ff551febef594d0b46a9a7affected · git
    • 174ae0a3b89e7804e4ea3d31bd83d6e43f39568c and later · before a14dbdf471001dd0601b0c491184990c178a199caffected · git
    • e49a51a96b531f1b4bcd8d358e645b6c74ef67e6 and later · before d22ad96f1a0c89e0ba66a2facc7430f0923919e3affected · git
    • cab63f64887616e3c4e31cfd8103320be6ebc8d3 and later · before 7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0affected · git
    • cab63f64887616e3c4e31cfd8103320be6ebc8d3 and later · before 7ef12e1dd06e442eebf370f6e53c41bd056d0f22affected · git
    • cab63f64887616e3c4e31cfd8103320be6ebc8d3 and later · before 6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cfaffected · git
    • cab63f64887616e3c4e31cfd8103320be6ebc8d3 and later · before 74be657d98a8d684c0475f3cbd450ef2a30ffc73affected · git
    • 5.10.201 and later · before 5.10.270affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93281Sep 24, 2026 · wifi: rtw89: fix HE extended capability length check
    0Monitor
  • ← EarlierCVE-2026-93282Sep 24, 2026 · ksmbd: fix maximum allowed access checks
    32Monitor
  • Later →CVE-2026-93284Sep 24, 2026 · drm/pagemap: dma-unmap pages before handling migration errors
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux20a2b6df91fd782ef2ff551febef594d0b46a9a7Vendor (CNA)
Linux Linux5.10.270Vendor (CNA)
Linux Linux5.15.221Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux5bf498623f8397d45f85f14cd631c5e5a565c2fbVendor (CNA)
Linux Linux6.1.188Vendor (CNA)
Linux Linux6.6Vendor (CNA)
Linux Linux6.6.157Vendor (CNA)
Linux Linux6ecf17bf5fe8da51a6e3fc9e03a76898fcc5c6cfVendor (CNA)
Linux Linux74be657d98a8d684c0475f3cbd450ef2a30ffc73Vendor (CNA)
Linux Linux7ef12e1dd06e442eebf370f6e53c41bd056d0f22Vendor (CNA)
Linux Linux7f8e2c4f3704d9774bb26b49b1ad6a60ae57d4a0Vendor (CNA)
Linux Linuxa14dbdf471001dd0601b0c491184990c178a199cVendor (CNA)
Linux Linuxd22ad96f1a0c89e0ba66a2facc7430f0923919e3Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records